address-current-branch-review
Skill501 starsChanged 18 days agoApache-2.0View on GitHub
Read unresolved GitHub code review threads for the pull request associated with the current branch, classify each comment, and implement and verify required code fixes. Post inline replies only when the user explicitly asks to reply after the changes have been pushed and are visible in the PR.
In this repository59 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/a11y.mdcCursor rule
- nx-generateSkill
- nx-importSkill
- nx-pluginsSkill
- nx-run-tasksSkill
- nx-workspaceSkill
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-exploreSkill
- openspec-proposeSkill
- openspec-sync-specsSkill
- api-designSkill
- celebration-scene-ideasSkill
- code-review-and-qualitySkill
- create-ticketSkill
- dep-scanSkill
- dep-triageSkill
- dial-docsSkill
- extract-to-libSkill
- figmaSkill
- fix-cve-backportSkill
- git-shipSkill
- i18n-stringsSkill
- lean-verificationSkill
- lib-themingSkill
- monitor-ciSkill
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-exploreSkill
- openspec-proposeSkill
- openspec-sync-specsSkill
- proactive-security-monitorSkill
- refactoring-auditSkill
- chat-release-notesSkill
- responsive-designSkill
- security-monitor-triagerSkill
- snyk-jira-ingestSkill
- snyk-scan-stubSkill
- snyk-triageSkill
- ui-kit-reviewSkill
- nx-generateSkill
- nx-pluginsSkill
- nx-run-tasksSkill
- nx-workspaceSkill
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-exploreSkill
- openspec-proposeSkill
- nx-generateSkill
- nx-importSkill
- nx-pluginsSkill
- nx-run-tasksSkill
- nx-workspaceSkill
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-exploreSkill
- openspec-proposeSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
39 rules. About 0 are common, 34 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈34
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Before posting a fix reply, verify that the relevant commit is pushed and included in the PR head.
- Distinctive: line 15
If the fix is not visible in the PR, do not post.
- Distinctive: line 20
Read repository instructions before editing.
- Very specific: line 21
Read root AGENTS.md and openspec/config.yaml.
- Very specific: line 26
Read the current branch and origin repository from local git.
- Distinctive: line 27
Prefer the GitHub app to find the open PR whose head matches the branch.
- Very specific: line 28
Use gh pr view only when the GitHub app cannot resolve it.
- Distinctive: line 29
Stop if there is no unique open PR for the branch.
- Very specific: line 32
Use the GitHub app review-thread action to get is_resolved, is_outdated, path, line, and replies.
- Distinctive: line 35
Do not assume flat comments represent thread resolution state.
- Distinctive: line 38
Read every reply already present in the thread.
- Distinctive: line 40
If code is fixed but unanswered, report that status.
- Distinctive: line 54
Keep every change traceable to a specific review thread.
- Distinctive: line 56
Do not commit, push, or force-update branches unless explicitly requested.
- Distinctive: line 59
Use Nx through the workspace package manager.
- Distinctive: line 61
Never claim a fix passed if the required command failed or was not run.
- Distinctive: line 62
If verification fails, continue fixing and do not post a success reply.
- Distinctive: line 66
Keep it concise and technical.
- Distinctive: line 69
Do not be defensive, over-apologetic, or vague.
- Distinctive: line 70
Do not use local-only or future-tense wording.
- Distinctive: line 72
Stop after implementation unless replies were explicitly requested.
- Distinctive: line 74
Do not call any GitHub reply/comment mutation.
- Distinctive: line 76
If and only if replies were explicitly requested, check PR visibility and post.
- Distinctive: line 78
Verify that the pushed PR head contains the relevant fix commit and that the fix appears in the PR diff.
- Distinctive: line 79
If the local fix is uncommitted, unpushed, or absent from the PR diff, stop without posting.
- Distinctive: line 80
Prefer the GitHub app inline reply action using the thread's top-level numeric review comment ID.
- Very specific: line 82
Use gh api graphql only as a fallback.
- Distinctive: line 84
Do not resolve threads, submit a review, approve, request changes, commit, or push unless explicitly requested.
- Distinctive: line 101
No code change needed:
- Distinctive: line 109
Never treat a request to fix review feedback as permission to post a GitHub reply.
- Distinctive: line 110
Never post a fix reply until the user explicitly asks for it after pushing.
- Distinctive: line 111
Never post a fix reply when the change is only local or unpushed.
- Distinctive: line 112
Never use “prepared locally,” “will appear after push,” or equivalent wording in a review reply.
- Distinctive: line 113
Never reply before understanding the full thread and current code.
- Distinctive: line 114
Never post a success reply for an unverified fix.
- Distinctive: line 115
Never fabricate test results, commit SHAs, or PR visibility.
- Distinctive: line 116
Never silently resolve a conversation.
- Distinctive: line 117
Never answer an ambiguous behavioral request on the reviewer's behalf.
- Distinctive: line 118
Never overwrite, unstage, or revert unrelated changes.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Address Current Branch Review
Process current-branch review feedback: inspect thread state, decide whether code must change, and verify any fix. Treat posting review replies as a separate, explicitly authorized action after push.
Reply Authorization Gate
- A request to fix, handle, address, or process review comments authorizes code changes only. It does not authorize posting GitHub comments.
- Post replies only when the user separately and explicitly asks to reply or answer the review comments.
- Before posting a fix reply, verify that the relevant commit is pushed and included in the PR head. Local working-tree changes or unpushed commits are never sufficient.
- If the fix is not visible in the PR, do not post. Tell the user to push first.
- Replies must describe the current PR state as already updated or fixed. Never post wording such as “prepared locally,” “will appear after push,” or any other future-tense visibility disclaimer.
Workflow
- Read repository instructions before editing.
- Read root
AGENTS.mdandopenspec/config.yaml. - Invoke
nx-workspacebefore exploring project ownership or targets. - Apply any area-specific skill required by the touched files.
- Read root
- Resolve the current pull request.
- Read the current branch and
originrepository from local git. - Prefer the GitHub app to find the open PR whose head matches the branch.
- Use
gh pr viewonly when the GitHub app cannot resolve it. - Stop if there is no unique open PR for the branch.
- Read the current branch and
- Load thread-aware review data.
- Use the GitHub app review-thread action to get
is_resolved,is_outdated, path, line, and replies. - Fetch flat PR comments for numeric comment IDs only when the user explicitly asked to post replies.
- Ignore resolved, outdated, approval-only, informational, bot-only, and duplicate threads.
- Do not assume flat comments represent thread resolution state.
- Use the GitHub app review-thread action to get
- Prevent duplicate work.
- Read every reply already present in the thread.
- Skip a thread if the requested change is already present in the current code and an adequate answer was already posted.
- If code is fixed but unanswered, report that status. Post the missing reply only after explicit reply authorization and the push check.
Classify each active thread.
Classification Action fix-requiredChange code, add or update tests, and verify. Do not reply unless authorized. reply-onlyDraft a technical explanation. Post it only when explicitly authorized. ambiguousDo not guess or post; ask the user for the missing decision. conflictingExplain the conflict and ask before changing behavior. - Implement
fix-requiredthreads.- Inspect the full affected file and related tests, not only the diff hunk.
- For multi-file work, build in thin vertical slices and verify each slice (see the task rules in
openspec/config.yaml). - Keep every change traceable to a specific review thread.
- Preserve unrelated user changes and staged files.
- Do not commit, push, or force-update branches unless explicitly requested.
- Verify each fix.
- Use Nx through the workspace package manager.
- Choose the smallest relevant tests first, then run project lint and build when appropriate.
- Never claim a fix passed if the required command failed or was not run.
- If verification fails, continue fixing and do not post a success reply.
- Draft a reply without posting it.
- Match the reviewer's language when practical.
- Keep it concise and technical.
- For a verified fix, state what changed and the relevant check.
- For
reply-only, explain why no code change is needed and reference the existing behavior or contract. - Do not be defensive, over-apologetic, or vague.
- Do not use local-only or future-tense wording.
- Stop after implementation unless replies were explicitly requested.
- Summarize local changes and verification to the user.
- Do not call any GitHub reply/comment mutation.
- If and only if replies were explicitly requested, check PR visibility and post.
- Fetch the current PR head SHA immediately before posting.
- Verify that the pushed PR head contains the relevant fix commit and that the fix appears in the PR diff.
- If the local fix is uncommitted, unpushed, or absent from the PR diff, stop without posting.
- Prefer the GitHub app inline reply action using the thread's top-level numeric review comment ID.
- Map GraphQL thread comments to numeric IDs through the flat PR comment list when necessary.
- Use
gh api graphqlonly as a fallback. - Post at most one new reply per processed thread.
- Do not resolve threads, submit a review, approve, request changes, commit, or push unless explicitly requested.
- Summarize.
- List fixed threads and whether each fix is visible in the PR.
- List replies posted only when posting was explicitly requested.
- List reply-only threads.
- List skipped or ambiguous threads.
- Report verification commands and any remaining warnings.
Reply Patterns
Verified and visible:
Updated: moved error handling to the global NotificationContext. Verified with `npm exec nx test chat` and `npm exec nx lint chat`.No code change needed:
No code change is needed here: the value is provided through an app-level adapter, so the library remains unaware of the REST path and preserves isolation.Safety Rules
- Never treat a request to fix review feedback as permission to post a GitHub reply.
- Never post a fix reply until the user explicitly asks for it after pushing.
- Never post a fix reply when the change is only local or unpushed.
- Never use “prepared locally,” “will appear after push,” or equivalent wording in a review reply.
- Never reply before understanding the full thread and current code.
- Never post a success reply for an unverified fix.
- Never fabricate test results, commit SHAs, or PR visibility.
- Never silently resolve a conversation.
- Never answer an ambiguous behavioral request on the reviewer's behalf.
- Never overwrite, unstage, or revert unrelated changes.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

