1,680 件 ・ 関連度順
概要と使いどころ
Comprehensive guide for writing modern Neo4j Cypher queries. Essential for text2cypher MCP tools and LLMs generating Cypher queries. Covers removed/deprecated syntax, modern replacements, CALL subqueries for reads, COLLECT patterns, sorting best practices, set-based writes, and Quantified Path Patterns (QPP) for efficient graph traversal.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive code review using specialized agents — orchestrates code, comments, tests, errors, types, and simplify agents sequentially.
日本語の概要は準備中です。原文の説明を表示しています。
Execute the implementation plan by processing and executing all tasks defined in tasks.md
日本語の概要は準備中です。原文の説明を表示しています。
Use when you've fixed a bug, added a feature, or made any user-facing change in a project that uses Towncrier and need to record it for the changelog — before committing or opening a PR, or whenever asked to add a changelog entry, towncrier fragment, or news fragment.
日本語の概要は準備中です。原文の説明を表示しています。
Code comment accuracy verification, documentation completeness assessment, comment rot detection.
日本語の概要は準備中です。原文の説明を表示しています。
Perform a dual-lens critical review of the specification and plan from both product strategy and engineering risk perspectives before implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Writes a single failing test that reproduces a bug after its root-cause analysis is complete, before any fix is written. TRIGGER when: a bug has a completed root-cause analysis and you need the failing reproduction test, writing a test that proves a bug exists, the second step of the bug-fixing pipeline. DO NOT TRIGGER when: still triaging or diagnosing the bug → opsmill-dev-analyzing-bugs; implementing the fix once the test exists → opsmill-dev-fixing-bugs; general feature test-first work → superpowers test-driven-development.
日本語の概要は準備中です。原文の説明を表示しています。
Opens a pull request, publishing the current branch as a PR. TRIGGER when: the user wants to open a pull request, publish the current branch as a PR, or take the current work through to an open PR. DO NOT TRIGGER when: only committing changes → commit; babysitting CI after the PR is already open → monitoring-pull-requests.
日本語の概要は準備中です。原文の説明を表示しています。
Watches an open pull request's CI until green and fixes failing checks. TRIGGER when: the user wants to watch a pull request's CI, babysit a PR until it goes green, or fix failing CI checks on an open PR. DO NOT TRIGGER when: opening the PR in the first place → pr; rebasing the branch onto its base → rebase.
日本語の概要は準備中です。原文の説明を表示しています。
Validate Jira/JPD ticket reference and create a feature branch
日本語の概要は準備中です。原文の説明を表示しています。
General code quality review — project guideline compliance, bug detection, code quality analysis.
日本語の概要は準備中です。原文の説明を表示しています。
Test coverage quality analysis — behavioral coverage, critical gap identification, test resilience evaluation.
日本語の概要は準備中です。原文の説明を表示しています。
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
日本語の概要は準備中です。原文の説明を表示しています。
Type design analysis — encapsulation, invariant expression, usefulness, and enforcement.
日本語の概要は準備中です。原文の説明を表示しています。
Module composition, state management, workspace strategy, provider versioning, and infrastructure-as-code best practices.
日本語の概要は準備中です。原文の説明を表示しています。
Pre-launch verification across infrastructure, security, legal, payment, email, analytics, and performance. Day-1 monitoring, rollback plan, incident response skeleton, and post-launch week-1 checklist.
日本語の概要は準備中です。原文の説明を表示しています。
Completion Check: Verify Infrastructure Is Wired
日本語の概要は準備中です。原文の説明を表示しています。
Design and implement Internal Developer Platforms (IDPs) with self-service capabilities, golden paths, and developer experience optimization. Covers platform strategy, IDP architecture (Backstage, Port), infrastructure orchestration (Crossplane), GitOps (Argo CD), and adoption patterns. Use when building developer platforms, improving DevEx, or establishing platform teams.
日本語の概要は準備中です。原文の説明を表示しています。
Reduces attack surface across OS, container, cloud, network, and database layers using CIS Benchmarks and zero-trust principles. Use when hardening production infrastructure, meeting compliance requirements, or implementing defense-in-depth security.
日本語の概要は準備中です。原文の説明を表示しています。
Configure security information and event management (SIEM) systems for threat detection, log aggregation, and compliance. Use when implementing centralized security logging, writing detection rules, or meeting audit requirements across cloud and on-premise infrastructure.
日本語の概要は準備中です。原文の説明を表示しています。
Apply and enforce cloud resource tagging strategies across AWS, Azure, GCP, and Kubernetes for cost allocation, ownership tracking, compliance, and automation. Use when implementing cloud governance, optimizing costs, or automating infrastructure management.
日本語の概要は準備中です。原文の説明を表示しています。
Optimize cloud infrastructure costs through FinOps practices, commitment discounts, right-sizing, and automated cost management. Use when reducing cloud spend, implementing budget controls, or establishing cost visibility across AWS, Azure, GCP, and Kubernetes environments.
日本語の概要は準備中です。原文の説明を表示しています。
Strategic guidance for operationalizing machine learning models from experimentation to production. Covers experiment tracking (MLflow, Weights & Biases), model registry and versioning, feature stores (Feast, Tecton), model serving patterns (Seldon, KServe, BentoML), ML pipeline orchestration (Kubeflow, Airflow), and model monitoring (drift detection, observability). Use when designing ML infrastructure, selecting MLOps platforms, implementing continuous training pipelines, or establishing model governance.
日本語の概要は準備中です。原文の説明を表示しています。
Build professional command-line interfaces in Python, Go, and Rust using modern frameworks like Typer, Cobra, and clap. Use when creating developer tools, automation scripts, or infrastructure management CLIs with robust argument parsing, interactive features, and multi-platform distribution.
日本語の概要は準備中です。原文の説明を表示しています。