Agent skill · writing content · aiskillstore
github-pr-best-practices
Best practices for creating GitHub pull requests including conventional commits, PR formatting, and multi-language support (en/ja). Use when creating PRs, writing PR descriptions, or formatting commit messages.
Why this skill is useful
Codifies best practices for PR creation and commit message formatting that the AI could infer but now doesn't have to guess.
What it needs
About 5k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
GitHub Pull Request Best Practices This Skill provides comprehensive guidance for creating high-quality pull requests following industry best practices and conventional commit standards. Capabilities Generate conventional commit formatted PR titles Structure PR descriptions with proper sections Support multiple languages (English/Japanese) Follow GitHub PR template conventions Avoid common PR mistakes When to Use Use this Skill when you need to: Create a new pull request Write PR titles and descriptions Format commit messages Follow conventional commit standards Generate PR content in English or Japanese PR Title Format Conventional Commits Standard PR titles must follow Conventional Commits format: Important: NO emojis in PR titles or descriptions. Common Types feat: New feature fix: Bug fix docs: Documentation changes style: Code style changes (formatting, no logic change) refactor: Code refactoring test: Adding or updating tests chore: Maintenance tasks, dependencies Scope (Optional but Recommended) The scope should indicate what part of the codebase is affected: Module name: feat(auth): add OAuth2 support Component name: fix(button): resolve click handler issue Area of code: docs(api): update endpoint documentation Description Use imperative mood ("add" not "added" or "adds") No capitalization of first letter No period at the end Clear and concise (under 50 characters when possible) Examples Good: Bad: PR Description Structure Standard Template Key Principles 1. Summary Section 1-3 bullet points maximum Explain what changed and why Avoid implementation details (those are in the code) Use present tense 2. Test Plan Section Use checkbox format (- [ ]) List specific test scenarios Include regression testing Be specific and actionable 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/github-pr-best-practices