github-pr

Creating a GitHub pull request with conventional commit standards requires structuring your PR title with a type and scope, such as `feat(user): implement profile page`. This Skill automatically enforces that structured commit message format while generating detailed PR bodies.

A conventional commit format for a pull request title prefixes the description with a type and optional scope, such as `feat(api): add user endpoint` or `fix(auth): resolve token expiry`. This structure clarifies the nature of changes for version control management.

Yes, you need the GitHub CLI installed to generate pull requests using this Skill. It relies on the GitHub CLI to handle the software development workflow and execute the actual pull request creation from your command line interface.

A detailed pull request description for code review should include a summary of changes, specific modifications made, and testing information. This ensures reviewers understand the context, verify the implementation, and validate the testing steps performed.

You can automate pull request creation and formatting directly from the command line using the GitHub CLI. This Skill streamlines the process by automatically generating formatted conventional commit titles and comprehensive PR bodies for your software development workflow.

You should use structured pull request titles in your software development workflow whenever you complete a new feature or bug fix. Enforcing conventional commit standards during code review preparation maintains clear version control history and communicates changes effectively.