github-pr-creation

The github-pr-creation skill is a specialized agent workflow designed for professional software engineers to streamline the process of opening pull requests. It integrates directly with local git environments and GitHub's command-line interface (gh) to ensure that PRs are high-quality, documented, and conform to project standards. Unlike standard agent behavior, this skill enforces a strict verification layer before submission, reducing noise in code reviews and preventing common mistakes like pushing to incorrect target branches or skipping critical test suites.

• Automatically identifies the correct base branch based on naming conventions (e.g., feature/* to develop, hotfix/* to main).

• Searches for and validates task documentation from sources like .s2s/plans, .kiro/specs, .cursorrules, GitHub Issues, and standard task files.

• Ensures task completion by checking sub-tasks against commit history, providing a summary report of pending work before creation.

• Enforces Conventional Commits standards for titles and descriptions, extracting scopes and types automatically from local commits.

• Performs pre-PR validation including running local test suites to ensure build integrity.

• Dynamically queries available GitHub labels and milestones, ensuring that the PR is correctly categorized and tracked according to project configuration.

• Use this skill whenever you are ready to submit your branch for peer review, release, or hotfix.

• Always confirm the target branch and review the generated PR content, including the automated body content, before final submission.

• The skill operates as a read-only analysis tool regarding your local files, ensuring safety while generating metadata for the GitHub API.

• It requires an authenticated gh CLI session to perform repository actions and fetch metadata like milestones or labels.

• Employs a HEREDOC pattern for PR body generation to maintain strict formatting and markdown integrity, ensuring compatibility with your team's pull request templates (e.g., feature, bugfix, release, or refactoring templates).