菜单
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".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use this skill to understand the claude marketplaces in the nsheaps github org: the plugin marketplace build, release, and propagation pipeline. Recall this skill when working on CI/CD workflows, mise tasks, plugin versioning, marketplace updates, or when asked how plugins get from source code to a user's Claude Code installation. Also recall when debugging version bumps, marketplace.json drift, or plugin cache issues.
Use this skill when the user asks about GitHub operations, pull requests, issues, releases, actions, gists, repos, or any task involving the GitHub CLI (gh). Also use when needing to interact with GitHub APIs, check CI status, review PRs, manage labels, create releases, or automate GitHub workflows from the command line.
Manually configure the GitHub App bot git identity the way the github-app plugin's SessionStart hook does — resolve the app slug and bot user ID, build the <slug>[bot] name and noreply email, set GIT_AUTHOR_*/GIT_COMMITTER_* env vars, and write an isolated GIT_CONFIG_GLOBAL with the gh auth git-credential helper. Use when commits are attributed to the wrong account, "Author identity unknown" appears, or git identity must be set up by hand. <example>my commits are showing up as the handler, not the bot</example> <example>git says Author identity unknown after the github-app hook ran</example> <example>configure the github app bot git identity manually</example> <example>set up the gh credential helper for git push</example>
Manually reproduce what the github-app plugin's SessionStart hook does to make a GitHub App installation token usable in the current session — materialize the PEM, generate the token, isolate GH_CONFIG_DIR, write the runtime env file, and wire CLAUDE_ENV_FILE so every Bash call sees GH_TOKEN/GITHUB_TOKEN. Use when the hook did not run, the token is missing from the environment, or a shell/teammate needs the token wired up by hand. <example>GH_TOKEN isn't set even though github-app is configured</example> <example>the github-app SessionStart hook didn't run, set up the token manually</example> <example>wire the github app token into CLAUDE_ENV_FILE</example> <example>gh keeps falling back to the wrong account, isolate GH_CONFIG_DIR</example>
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>
Manages spec files for requirements capture and validation
| name | pr-workflow |
| description | 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". |
| allowed-tools | Bash, Read, Grep, Glob |
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 |