From claude-commands
Enforces PR descriptions to include a full GitHub URL to a governing roadmap/design doc and a `br` bead ID for production code changes under CI gates or ZFC/level-up behavior.
How this skill is triggered — by the user, by Claude, or both
Slash command
/claude-commands:pr-body-design-docThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
For any PR that changes production code under `$PROJECT_ROOT/**`, CI gates, or ZFC/level-up behavior, the PR description **must** include:
For any PR that changes production code under $PROJECT_ROOT/**, CI gates, or ZFC/level-up behavior, the PR description must include:
roadmap/*.md or docs/design/** file on $GITHUB_REPOSITORY, or the literal N/A with a one-line justification (docs-only typos, etc.).br bead ID (e.g. rev-xxxxx) or N/A with justification.Level-up or rewards_engine / world_logic work must also cite the canonical design + task-spec links:
Repo default template: your-project.com → .github/pull_request_template.md. CI does not parse PR bodies for these links; design-doc-gate.yml enforces code grep gates only—human and agent discipline fills the gap.
npx claudepluginhub jleechanorg/claude-commands --plugin claude-commandsStandardizes br bead follow-ups for PR/code reviews with exact implementation instructions, API/function signatures, and acceptance criteria.
Drafts reviewer-first PR descriptions that lead with why, prove claims with evidence, name load-bearing files, and stay honest about blast radius.
Rewrites PR titles or descriptions on strapi/documentation repos to match project git-rules. Used via `/pr-fix` with explicit action and optional PR identifiers or auto-detection of recent PRs.