plugins/scm-utils/skills/pr-workflow/SKILL.md
Full PR lifecycle management: creating, iterating on feedback, and merging. Triggers on: "review my PR", "iterate on PR feedback", "address review comments", "PR workflow", "get this merged", "respond to reviewer", "handle PR feedback".
npx skillsauth add nsheaps/ai-mktpl pr-workflowInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
End-to-end PR lifecycle from creation to merge. See also: request-a-review, pr-feedback.
request-review label for CI review botrequest-a-review skill for PR body format and gh api commandsBefore making any code changes, reply to each reviewer thread:
NEVER re-request review without responding to all open threads first.
gh api repos/<owner>/<repo>/pulls/<PR>/reviews \
--hostname github.com \
--method POST \
--field body="Addressed in latest commit. [details]" \
--field event="COMMENT"
Use gh pr review --comment for formal reviews; use inline replies for specific thread responses.
~/src/nsheaps/{repo}.worktrees/{branch}/git merge origin/mainAfter responding to all threads AND pushing fixes:
gh pr edit <PR_NUMBER> --add-label "request-review"
Minimize stale review comments where applicable.
Only after handler explicitly says yes:
gh pr merge <PR_NUMBER> --squash --delete-branch --hostname github.com
| Rule | Detail | | ------------------------------------------ | ---------------------------------------------------------- | | No rebase on pushed branches | Merge main instead | | No force push | Add commits on top | | Always respond before re-requesting review | Non-negotiable | | Never merge without handler approval | STRIKE ONE — asking then acting before answer is worse | | Review sub-agent diffs | Before reporting PR as fixed |
tools
Reference material for Claude Code internals — the on-disk layout under ~/.claude and project-scope .claude, the plugin cache, session-env propagation, and the full hook lifecycle. Auto-recall when working on Claude-Code-related tasks: writing or debugging hooks, authoring plugins, inspecting session state, troubleshooting why an env var is or isn't visible to a Bash tool call, or when paths under ~/.claude or ~/.claude/plugins/ come up.
development
Manage GitHub App installation tokens in Claude Code sessions. Use when tokens expire, auth errors occur in long-running sessions, or when setting up GitHub App credentials for agent teams. <example>my github token expired</example> <example>refresh the github app token</example> <example>check token status</example> <example>set up github app authentication for this session</example>
tools
Auto-detect project formatting tools and configure edit-utils settings
tools
Use this skill when the user asks about 1Password, secrets management, retrieving credentials, using op CLI, service accounts, secret references, vault operations, or any task involving the 1Password CLI (op). Also use when needing to inject secrets into environment variables, read passwords or API keys from 1Password, or manage 1Password items from the command line.