Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From copilot-cli-toolkit
Validates PR titles for conventional commit format (<type>(<scope>)?: <description>), bodies for issue linking keywords (Closes/Fixes #N), and template compliance (Summary, Changes, Type of Change).
How this skill is triggered — by the user, by Claude, or both
Slash command
/copilot-cli-toolkit:validate-pr-descriptionThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
- PR title: [User provides]
Validate the PR description against these standards:
Title must match <type>(<scope>)?: <description> where type is one of:
feat, fix, docs, style, refactor, perf, test, chore, ci, build, revert.
Body should contain at least one issue linking keyword:
Closes #N, Fixes #N, Resolves #N (and their past-tense variants).
These keywords auto-close the linked issue when the PR merges on platforms that support them (GitHub, GitLab). On other platforms (Azure DevOps, Bitbucket), they serve as traceability markers.
Check that required sections are populated:
If .claude/skills/github/scripts/pr/validate_pr_description.py exists, run it:
python3 .claude/skills/github/scripts/pr/validate_pr_description.py \
--title "[title]" \
--body-file "[path-to-body.md]"
Otherwise, validate manually against the criteria above.
Report findings with actionable recommendations for any failures.
npx claudepluginhub p/rjmurillo-copilot-cli-agents-src-copilot-cliRewrites PR titles or descriptions on strapi/documentation to match git-rules.md. Uses gh CLI for listing and editing, with support for batch or single PRs.
Generate a comprehensive pull request description following the repository's standard template. Use when the user wants to create or update a PR description.
Crafts PR titles using conventional commits format. Automates release-please versioning and ensures consistent git history through squash-and-merge.