Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →aiskillstore/github-pr-best-practices
Best practices for creating GitHub pull requests including conventional commits, PR formatting, and multi-language support (en/ja).
Passed 19 of 22 test cases with the skill, and 14 of 22 without it.
and 2 more in the full report
5 fixed14 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
I restructured the database query module to improve performance without changing any existing features or fixing bugs. What conventional commit type should be used for the PR title?
| Checked | Without skill | With skill |
|---|---|---|
| The PR title uses the refactor commit type. | Missed | Passed |
| The PR title scope specifies database or db. | Passed | Passed |
The instructions your model reads when the skill loads.
This Skill provides comprehensive guidance for creating high-quality pull requests following industry best practices and conventional commit standards.
Use this Skill when you need to:
PR titles must follow Conventional Commits format:
<type>(<scope>): <description>
Important: NO emojis in PR titles or descriptions.
feat: New featurefix: Bug fixdocs: Documentation changesstyle: Code style changes (formatting, no logic change)refactor: Code refactoringtest cases passed, vs 14 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.