GitHub Pull Request Workflow

Upstream attribution: Adapted from the original github-pr skill authored by Dan Webb in damacus/skills commit b97d545.

Use this skill to take an explicitly selected local change through a conventional commit, push, and GitHub pull request. main is always the base branch. Do not discover or substitute another default branch unless the user explicitly overrides this rule.

Run GitHub CLI commands with elevated network access. Check gh auth status before the first GitHub write and ask the user to run gh auth login if authentication fails.

Workflow

1. Inspect the work and current publication state

• Inspect git status --short, git diff, and git diff --cached before staging anything.
• Identify the exact files that belong to the requested work. Preserve unrelated staged, unstaged, and untracked changes.
• Check whether the current branch already has a PR with gh pr list --head <branch> --state all. If it has an open PR, verify and summarize that PR instead of creating a duplicate. If it is closed or merged, do not reuse the branch without explicit user direction.
• Refresh origin/main before creating a new feature branch. Do not silently rebase, reset, stash, or rewrite any worktree state.

2. Create or verify the feature branch