メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
Detect violations of architectural decisions in the codebase. Checks module dependency direction rules, identifies boundary violations, and reports drift between documented decisions and actual code.
| name | pr-check |
| description | 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. |
| allowed-tools | Read, Bash(gh *), Bash(git *), Bash(bash plugins/*) |
| user-invocable | true |
Validate that a pull request follows principled conventions for cross-referencing, labeling, and description quality.
/pr-check [<pr-number>] [--strict] [--json]
| Argument | Required | Description |
|---|---|---|
<pr-number> | No | PR number to check. Defaults to the current branch's open PR. |
--strict | No | Fail on warnings (by default, only errors cause failure). |
--json | No | Output results as JSON instead of human-readable text. |
gh CLI must be installed and authenticatedResolve PR. Determine which PR to check:
<pr-number> provided: use it directlygh pr view --json numberFetch PR metadata. Get PR details:
bash scripts/fetch-pr-metadata.sh --pr <number>
Returns: title, body, labels, base branch, head branch, file count, and file paths.
Run checks. Execute each validation:
bash scripts/validate-pr.sh --pr-body "<body>" --pr-labels "<labels>" --branch "<head-branch>" --files "<files>" [--strict]
The script checks:
Required (errors):
## Summary section## Test plan or ## Checklist sectionRecommended (warnings, errors in --strict):
Closes #N, Fixes #N, Relates to #N)Plan-NNN) or proposal (RFC-NNN)type:*, plan:*, proposal:*)impl/, feat/, fix/)Report results. Display check results:
--json: structured JSON outputscripts/check-gh-cli.sh --- Verify gh CLI availability (copy)scripts/fetch-pr-metadata.sh --- Fetch PR details from GitHubscripts/validate-pr.sh --- Run PR validation checks