devbasex

cherry-pick-pr

Cherry-pick a merged fix onto an environment branch (qa/staging, release) as a new PR. 明示指示のみで実行する。Use when the same fix must reach qa or staging（qaにも同じ修正を適用・stagingにも反映・cherry-pick）.

DevOps & Infrastructure Listed

deploy

Create a deploy PR to an environment branch such as qa/staging. 明示指示のみで実行する。Use when deploying to an environment branch（qaに上げる・stagingへデプロイ）.

pr-review

Review a PR diff, or the branch diff with --branch, and post an approve or request-changes verdict. Use when reviewing a PR（PRレビュー・マージ前チェック・セルフレビュー）.

statusline

Switch, restore, or inspect the NDF statusline in the Claude Code settings. 明示指示のみで実行する。Use when changing the statusline（statusline切り替え・ステータスライン）.

cross-refactoring

Let several CLIs propose, apply, and review refactorings on a PR until no new proposal appears. Use when structural improvement should converge across runtimes（クロスリファクタリング・多AIリファクタリング・収束リファクタリング）.

cross-review

Review a PR with both Codex and Gemini, looping fixes until both APPROVE. Use when a converging two-AI review is wanted（クロスレビュー・両AIレビュー・収束レビュー）.

fix

Fix actionable PR review comments, then reply and resolve each thread. Use when responding to review feedback on a PR（PRコメント対応・PRレビュー修正・Resolveして）.

issue-plan-strategy

Turn an issue into a plan and run it through a release branch and multiple PRs. Use when designing or executing a plan（issueのplanを作って・planを実行・multi-PRで進めて）.

logging-guidelines

Choose log levels and keep secrets and personal data out of logs. Use when adding or reviewing logging（ログ追加・ログレベルを決める・ログ設計）.

Data & Documents Listed

markdown-writing

Write Markdown docs, specs, PR bodies, and reports for a third-party reader, with tables and mermaid. Use when authoring or editing a Markdown document（ドキュメント作成・仕様書を書く・PR本文）.

merged

Delete merged branches and worktrees after listing them for approval, then update main. Use when a PR was merged（マージ後の後片付け・ブランチを整理・worktreeを削除）.

Data & Documents Listed

official-skills-autoloader

Install an official Anthropic Skill (docx / pptx / xlsx / pdf) on demand, showing the source first. Use when Office or PDF output is needed（Word作成・Excel出力・PDF作成）.

plan-to-spec

Rewrite a finished implementation plan into a permanent specification under docs/. Use when implementation is complete（planを仕様書にして・確定仕様書に移動）.

Commit, push, and open or update a pull request, draft included, after showing branch and files for approval. Use when asked to create or update a PR, or to push work for review（PRを作って・コミットしてプッシュ・PRを更新）.

redash-guide

Redash MCP プラグインの使い方ガイド

DevOps & Infrastructure Listed

docker-container-access

Diagnose container access and localhost routing failures, including DinD/DooD. Use when a container is unreachable（コンテナに接続できない・localhostが繋がらない）.

DevOps & Infrastructure Listed

ndf-policies

Core NDF project policies. 知識として参照するだけで、手順として実行しない。判断に迷ったときの基準として使う: ブランチ戦略、環境ブランチ (qa/staging/release) へ同じ修正を適用する原則、feature ブランチを汚さない運用、PR 運用ルール。

pr-tests

Run the test plan written in a PR body and post the results as a PR comment. Use when a PR test plan has to be executed（PRのテストを実行・テストプランを実行・テスト結果をPRにコメント）.

redash-add

任意 suffix の Redash MCP を project .mcp.json に追加する

redash-list

現在有効な Redash MCP を一覧表示する

redash-remove

指定 suffix の Redash MCP を project .mcp.json から削除する

redash-status

Redash MCP の設定状況と環境変数の確認

development-workflow

Classify a change into 4 workflow modes and route it to the required steps. Use when deciding how much process a change needs（モード判定・工程の振り分け）.

external-ai

Delegate coding, review, or research to the codex, gemini, kiro-cli, or claude CLI. Use when a second opinion or an offloaded investigation is wanted（codexで調査・geminiレビュー・外部AIに投げて）.

implementation-plan

Create or update an implementation plan under issues/ before coding. Use when a change spans files, adds a feature, or migrates the DB（実装プラン・実装を開始・設計書を作成）.

investigation-rules

Never claim something is absent without showing the search behind it. Use when writing an investigation or bug report（調査レポートを書く・不具合レポート・カラムがない）.

problem-solving

Fix bugs and data inconsistencies upstream at the root cause. Use when a bug or outage needs a fix decision（バグの根本原因・データ不整合・障害対応）.

refactoring

Change structure without changing behavior, guarded by tests, judging smells and how decisions are represented. Use when cleaning up code or touching legacy code（リファクタリング・コードスメル・分岐をデータ化・現状固定テスト）.

Web & Frontend Listed

requirements-design

Turn a vague request into verifiable acceptance criteria before implementing. Use when the done-condition is unclear（受け入れ条件・要求を整理・成功条件）.

tdd-cycle

Write a failing test first, then the smallest implementation that passes. Use when adding behavior or fixing a bug（テスト駆動・先にテスト・再現テスト）.

qa-security-scan

Run an OWASP Top 10 review of code, auth, and data protection. Use when a security review or vulnerability check is asked for（セキュリティレビュー・脆弱性チェック・認証認可の確認）.