Stats
Actions
Tags
From sentinel
Implement review feedback on a PR. Checks out the branch, applies reviewer-requested changes, runs preflight, commits, and pushes. Triggers on: impl-review, implement review, implement review feedback, address review comments.
How this skill is triggered — by the user, by Claude, or both
Slash command
/sentinel:impl-reviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Checkout a PR's branch, implement the reviewer's feedback, run preflight checks,
Checkout a PR's branch, implement the reviewer's feedback, run preflight checks, commit, and push.
<pr-number> (required) -- The PR number to implement review feedback
for. The repo is auto-detected from the current directory.Always ask for user confirmation before implementing changes, before committing/pushing, and before posting comments on GitHub.
REPO=$(gh repo view --json nameWithOwner -q .nameWithOwner)
Use $REPO for all gh and gh api commands throughout.
Extract the PR number from the arguments. It must be a numeric value. If no PR number is provided, ask the user for one.
gh pr view $PR_NUMBER --repo $REPO --json headRefName,title,body,state,files,baseRefName
Extract:
headRefName) -- the branch to checkoutOPEN (abort if closed/merged)If the PR is not open, inform the user and stop.
Fetch review data from the PR:
gh api repos/$REPO/pulls/$PR_NUMBER/reviews --paginate
gh api repos/$REPO/pulls/$PR_NUMBER/comments --paginate
gh api repos/$REPO/issues/$PR_NUMBER/comments --paginate
This provides:
Parse the review comments to understand what changes are requested:
Identify actionable feedback -- Focus on explicit change requests from reviewers. Ignore:
Categorize each requested change:
Present the plan:
git fetch origin
git checkout <headRefName>
git pull origin <headRefName>
Ensure you're on the correct branch and up to date with the remote.
CRITICAL: Only make changes the reviewer explicitly asks for.
Invoke the preflight skill to validate all changes:
/preflight
This runs format, lint, build, and affected tests (auto-detected for the project type).
If preflight fails:
Before committing, show the user a summary of all changes (files modified, diff stats) and ask for confirmation. If the user rejects, stop without committing.
ALWAYS create a NEW separate commit -- never amend existing commits.
git add <changed-files>
git commit -m "$(cat <<'EOF'
Address review: <brief description of changes>
EOF
)"
git push
Commit message guidelines:
Co-Authored-By line--no-verify or --no-gpg-sign flagsIf multiple logical units of review feedback were addressed, consider separate commits for each.
Show the draft comment to the user and ask for confirmation before posting. If the user rejects, skip posting.
Post a summary comment on the PR:
gh pr comment $PR_NUMBER --repo $REPO --body "$(cat <<'EOF'
Fixed: <description of what was changed>
<For each review point addressed, briefly note what was done>
EOF
)"
Output a summary to the user:
Co-Authored-By lines in commits/impl-review 12345
Asks for confirmation before implementing, committing, and posting.
npx claudepluginhub luciferdono/sentinelGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.