github-pr

To create a GitHub pull request with standardized formats, use this skill to generate predefined title structures and body templates. It enforces consistent naming conventions and includes sections for summaries, issue links, and testing checklists.

You can automatically link a GitHub pull request to a specific issue by including the issue number in the PR title. This skill enforces issue linking by generating titles like '[#123] Implement user login' to connect PRs to their respective issues.

Yes, you need the GitHub CLI (`gh`) installed and authenticated to automate pull request creation. This skill relies on the `gh` command-line tool to execute workflows and submit PRs directly from your development environment.

The best way to ensure consistent PR documentation is to enforce body templates and standardized naming conventions. This skill provides workflow guidance for feature development and bug fixes, requiring summaries, issue links, and testing checklists for every submission.

Yes, you can use this pull request workflow for both feature development and code reviews. It supports multiple use cases by applying standardized templates and issue linking to ensure all code review submissions adhere to project documentation standards.

A GitHub pull request body template should include a summary of changes, a link to the relevant issue, and a testing checklist. This skill generates these body templates automatically to ensure all necessary documentation is present before submission.