github-pr-best-practiceslisted

# 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](https://www.conventionalcommits.org/) format: ``` <type>(<scope>): <description> ``` **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 capit