▸ Agent Skills

GitHub

GitHub and git workflows via the gh CLI.

Sections

  • gh-create-issue — Create structured GitHub issues from conversation context using gh CLI
  • gh-create-pr — Generate a PR title and description, then commit, create/update the PR on approval
  • gh-release-notes — Generate human-readable release notes for a version from the merged history and cut a GitHub release with the gh CLI - gather the commit and PR range since the last tag, group changes by type, write curated notes, and publish. Use when the user wants to cut a release, tag a version, write a changelog or release notes, or summarise what shipped since the last tag. Pairs well with conventional-commit history but does not require it.
  • gh-resolve-pr-comments — Triage and resolve GitHub PR review comments with categorized action plans and approval-gated execution
  • gh-submit-review — Post a completed code review to a GitHub PR via the gh CLI - pick the event (approve, request-changes, or comment), attach inline line comments, and a summary body. Use when you have finished reviewing someone else's PR and need to submit the verdict, when a review pass (such as code review or edge-case probing) produced findings to publish, or when the user asks to approve, request changes on, or leave review comments on a pull request.
  • gh-triage — Triage a GitHub backlog - move issues and external PRs through a state machine of triage roles (categorise, verify, grill if needed, write agent-ready briefs) using the gh CLI and GitHub labels. Use when triaging your GitHub issues and PRs, deciding what's ready for an agent or a human, or turning a backlog into agent-ready briefs.
  • git-resolve-conflicts — Resolve merge conflicts systematically with context-aware 3-tier classification and escalation protocol
  • git-update-branch — Bring a feature branch up to date with its base branch safely - fetch first, detect the base, choose rebase vs merge deliberately, use --force-with-lease, and hand conflicts off cleanly. Use when a branch has fallen behind its base, when the user wants to rebase or merge in the latest from the base/default branch, when a PR reports merge conflicts or an out-of-date branch, or when deciding between rebase and merge for an update.