メニュー
Generate or update a CODEOWNERS file from the repository's module structure and git history. Maps module boundaries to code ownership using principled documentation structure as the guide. Use when setting up or refreshing code ownership rules.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Validate that a pull request follows principled conventions: references a plan or proposal, has correct labels, includes required sections in the description, and links to relevant documents. Use in CI or before merging to enforce PR quality.
Generate a structured pull request description from a DDD plan task. Reads the plan, task manifest, and implementation branch to produce a PR body with references to the originating proposal, plan, ADRs, and related tasks. Use when opening a PR for plan-driven work.
Process open GitHub issues through the principled pipeline. Lists untriaged issues, normalizes their metadata, ingests them into the documentation pipeline, and reports a summary. Operates as the batch entry point — delegates to /ingest-issue for each individual issue.
Implementation orchestration strategy for the Principled framework. Consult when working with DDD plan execution, git worktrees for task isolation, task manifests, or the decompose-spawn-validate-merge lifecycle. Covers worktree management, sub-agent patterns, task state machines, and manifest schema.
Top-level orchestrator for DDD plan execution. Decomposes a plan into tasks, iterates through phases respecting dependencies, spawns worktree-isolated agents, validates implementations, and merges results. Runs inline to coordinate multiple sub-agent spawns. Use for automated end-to-end plan execution.
Audit ADR coverage across modules. Identifies modules with no architectural governance, orphaned ADRs referencing removed modules, and stale architecture docs. Classifies findings by severity.
| name | gen-codeowners |
| description | Generate or update a CODEOWNERS file from the repository's module structure and git history. Maps module boundaries to code ownership using principled documentation structure as the guide. Use when setting up or refreshing code ownership rules. |
| allowed-tools | Read, Write, Bash(git *), Bash(ls *), Bash(bash plugins/*) |
| user-invocable | true |
Generate or update a .github/CODEOWNERS file from the repository's module structure and git history.
/gen-codeowners [--modules-dir <path>] [--output <path>] [--dry-run]
| Argument | Required | Description |
|---|---|---|
--modules-dir <path> | No | Root directory containing modules. Defaults to auto-detection. |
--output <path> | No | Output path. Defaults to .github/CODEOWNERS. |
--dry-run | No | Print the generated CODEOWNERS without writing. |
Detect modules. Scan for directories containing CLAUDE.md, docs/, or package.json:
bash scripts/detect-modules.sh [--modules-dir <path>]
Returns a list of module paths.
Analyze ownership. For each module, determine primary contributors:
bash scripts/analyze-ownership.sh --module <module-path>
Uses git shortlog -sne on the module directory to rank contributors by commit count.
Read existing CODEOWNERS. If .github/CODEOWNERS exists, parse it to preserve:
# manual comment)Generate CODEOWNERS. Read templates/codeowners.txt as a structural guide and produce:
docs/ directories)Write or display. Based on flags:
--dry-run: write to output path--dry-run: display generated contentReport results. Summary of:
scripts/detect-modules.sh --- Find module directories in the repositoryscripts/analyze-ownership.sh --- Determine code ownership from git historytemplates/codeowners.txt --- Structural template for CODEOWNERS file