devbasex
OrganizationAI Agent Marketplace - Claude Codeプラグインマーケットプレイス
Categories
Indexed Skills (51)
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）.
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レビュー・マージ前チェック・セルフレビュー）.
install-wrapper
Install, remove, or inspect the NDF relay for Claude Code. 明示指示のみで実行する。Use when setting up or removing the relay that restarts claude at section breaks（中継を入れる・中継を外す・中継の状態）.
statusline
Switch, restore, or inspect the NDF statusline in the Claude Code settings. 明示指示のみで実行する。Use when changing the statusline（statusline切り替え・ステータスライン）.
cross-refactoring
Let every CLI propose refactorings on a PR once, then one CLI plans, tests, applies, and verifies what fits a time budget. Use when structural improvement should be done across runtimes within a set time（クロスリファクタリング・多AIリファクタリング・時間内の構造改善）.
cross-review
Review a PR with two CLIs picked from claude, codex, kiro and the host (agy only with --include agy), looping fixes until no new finding appears. Use when a converging multi-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, write the execution plan for several issues, and run them through a release branch and multiple PRs. Use when designing or executing a plan, or when several issues are handed over at once（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（ログ追加・ログレベルを決める・ログ設計）.
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, stopping only where git refuses, then update the base branch. Use when a PR was merged（マージ後の後片付け・ブランチを整理・worktreeを削除）.
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を仕様書にして・確定仕様書に移動）.
pr
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を更新）.
document-drafting
Write the body of a business document in Markdown, following what its type requires. Use when writing a proposal, approval request, report, metric definition, manual or briefing（執筆・提案資料を書く・稟議書を書く・マニュアルを書く）.
document-restructuring
Rebuild a finished document from its outline: measure, reorder chapters into the reader's question order, tighten sentences, measure again. Use when a document is written and before it goes to review（ドキュメント再構成・章立てを組み直す・読みやすさを測る）.
document-sources
Fix where every number, figure and quotation comes from, so the same value can be reached again. Use when a business document carries data（素材の収集・出典を確定する・数値の出所・引用元）.
document-systems
Hold the per-system steps for reading, posting and rendering documents in Google Drive, Notion, Confluence, SharePoint or the repository itself. Use when a document must be fetched from or published to one of them（ドキュメンテーションシステム・Confluenceへ投稿・SharePointから取り込む・システムごとの手順）.
google-auth
Set up OAuth2 credentials for Google APIs (Drive, Docs, Sheets). Use when a token is missing or expired（Google認証・OAuth2認証・client_secret）.
google-drive
Export, download, upload, and share Google Drive and Docs files. Use when a file must be fetched from or published to Drive（Google Drive・Google Docs・共有リンク）.
issue-upkeep
Bring the existing issue list back in line with reality: fix stale bodies, assign milestones, and close what is not worth doing. Use when a change is finished and the issue list has drifted（課題の棚卸をするとき・issueの手入れ・やらないと決める）.
layout-review
Render the generated document and look at the result, to catch what reading the source cannot show. Use when a document has been generated and before it is submitted（体裁レビュー・版面を見る・描画して確かめる・文字あふれ）.
ml-model-structure
Lay out ML training and inference code as versioned directories with a feature SSoT. Use when building or retraining a model（モデル構築・モデル再学習・推論API）.
out-of-scope
Capture a finding outside the current scope as an issue at the moment it is found. Use when a defect or improvement appears outside what this change fixes（範囲外の課題・その場で起票・対象外と判断した指摘）.
progress-tracking
Record which development stage an issue has reached, in the issue body and on the board. Use when entering a stage of the workflow（進行を記録・工程の記録・どこまで進んだか）.
release-verification
Verify a released version in the user's own environment after distribution. Use when a merged change has been released and has to be checked for real（リリース後テスト・配布後の実機確認・本番での受け入れ確認）.
release
Make merged changes reach users by publishing, deploying, or submitting, depending on what is distributed. Use when a merged set has to be delivered（配布する・リリースする・デプロイする）.
restart
Restart claude with a resume command: under the NDF relay the switch is automatic, otherwise show the steps and the text to paste. Claude Code only. Use when plugin updates must take effect or the context should be cut（再起動・会話を切り替える・プラグインの更新を反映）.
retrospective
Record what to change in how the work was done, and pick up findings that were never filed. Use when a change has been released and verified（振り返り・進め方の見直し・起票の取りこぼしを拾う）.
skill-stats
Measure Skill usage from Claude Code transcripts: invocations, trigger hit rate, per-Skill breakdown. Use when auditing which Skills fire（skill統計・skill利用分析）.
redash-guide
Redash MCP プラグインの使い方ガイド
docker-container-access
Diagnose container access and localhost routing failures, including DinD/DooD. Use when a container is unreachable（コンテナに接続できない・localhostが繋がらない）.
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にコメント）.
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（モード判定・工程の振り分け）.
redash-add
任意 suffix の Redash MCP を project .mcp.json に追加する
redash-list
現在有効な Redash MCP を一覧表示する
redash-remove
指定 suffix の Redash MCP を project .mcp.json から削除する
redash-status
Redash MCP の設定状況と環境変数の確認
external-ai
Delegate coding, review, or research to the codex, agy, kiro-cli, or claude CLI. Use when a second opinion or an offloaded investigation is wanted（codexで調査・agyレビュー・外部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（リファクタリング・コードの兆候・分岐をデータ化・現状固定テスト）.
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（テスト駆動・先にテスト・再現テスト）.
language-servers
Set up Serena language servers, once per project. Use when this repository has no Serena languages or the session start notice reports a mismatch: detects languages, writes .serena/project.yml, verifies each server, checks Claude Code LSP（言語サーバを設定・Serenaの言語を直す）.
design
Write the design document before coding: data structures, interface contracts, decisions. Use when a change needs a design step（設計書を作る・データ構造を決める・APIの契約を決める）.
notion-writing
Write Notion pages in Notion-flavored Markdown: XML tables with fixed column widths, and edits that never delete child pages. Use when creating or editing a Notion page（Notionページ作成・Notionテーブル・Notionに書き出す・子ページ）.
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（セキュリティレビュー・脆弱性チェック・認証認可の確認）.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.