github-pr

name	github-pr
description	Automates the end-to-end Git workflow: branch creation, staging, committing, pushing, and opening or updating a GitHub pull request. Use when a feature or fix is ready for review and requires a structured PR, or when branch changes may need to be pushed to an existing PR for follow-up review.

GitHub Workflow

This skill guides the process of moving local changes to a GitHub Pull Request.

Prerequisites

• git must be installed and configured.
• gh (GitHub CLI) must be installed and authenticated.

Commit Message Format

Use Conventional Commits with this required format: <type>(<scope>): <summary>

• type REQUIRED. Common values: feat, fix, docs, refactor, chore, test, perf, ci, build, style.
• scope REQUIRED. Short noun for the changed area (for example: config, api, ui, docs).
• summary REQUIRED. Imperative, <= 72 chars, no trailing period.

Rules:

• Never add AI attribution anywhere in the GitHub workflow. Do not write Generated by ..., Co-authored-by: Claude, Co-authored-by: Opus, Co-authored-by: Sonnet, or any other AI/model/agent attribution.
• This ban applies to commit subjects, commit bodies, commit footers, PR titles, PR bodies, and PR comments. Do not add it even if a default template, tool, model habit, or previous workflow suggests it.