rarestg/github-review-workflow
skills/github-review-workflow/SKILL.md
Export a PR's clean inline review comments, CodeRabbit outside-diff comments, and CodeRabbit nitpicks into local files, then triage review feedback through a stack-aware orchestrator workflow with durable reply drafts for follow-up PRs. Use when given a GitHub pull request URL and asked to work through review comments without relying on noisy raw API blobs.
$ install --global
skillsauthnpx skillsauth add rarestg/rarestg-skills github-review-workflowInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 20, 2026, 6:03 AM147.7s10 files scanned
SKILL.md
- name:
- github-review-workflow
- description:
- >-
- disable-model-invocation:
- true
- allowed-tools:
- Bash, Read, Write, Edit, Glob, Grep, Agent
- argument-hint:
- <pr-url>
- user-invocable:
- true
GitHub Review Workflow
Export inline PR review threads into a local queue, export CodeRabbit
outside-diff comments and nitpicks into separate local-only queues, then follow
this skill's stack-aware orchestration workflow in references/SOP.md.
Prerequisites
ghinstalled and authenticatedpython3available in the shell- the current working directory is the project that owns the PR
Export
Set SKILL_DIR to this skill's installed or repo-local path, then run:
python3 "$SKILL_DIR/scripts/export_github_review_comments.py" <pr-url>
Useful export flags:
--include-resolvedto reprocess already-resolved threads--include-ai-promptsto preserve embedded AI-agent prompt sections; they are stripped by default
Read the full bundle before editing:
$SKILL_DIR/references/SOP.md.github-review-workflow/pr-<number>-<slug>/README.md.github-review-workflow/pr-<number>-<slug>/context/01-coderabbit-walkthrough.mdif it exists- all files in
.github-review-workflow/pr-<number>-<slug>/todo/ - all files in
.github-review-workflow/pr-<number>-<slug>/outside-diff/if it exists; triage them as local-only review-summary items because GitHub could not post them inline - all files in
.github-review-workflow/pr-<number>-<slug>/nitpicks/if it exists; triage them as lower-priority local-only items unless the user asked to handle them now
Defaults
- For stacked PR review-comment cleanup, accepted fixes land in a new PR stacked above the current top PR. Do not amend, rebase, force-push, or otherwise update older reviewed PR branches for these fixes.
- If the reviewed PR is not part of a stack and the user did not ask for PR follow-through, keep code changes local and use the direct follow-up script.
- Fixed stacked-review replies are queued locally until the follow-up PR exists,
then posted as
Addressed in <fix-pr-url>: <summary>. - Declined or obsolete thread-backed comments use the same durable queue and may
be posted immediately as
Not taking this change: <reason>. - Triage up front: judge merit, group related items, detect conflicts or ordering, and decide what is worth delegating.
- Do a lightweight stack/base check before editing; deepen it only when the current branch, PR head, stack top, or intended fix branch is ambiguous.
- The orchestrator owns the queue. Implement small, obvious fixes directly.
- Delegate only bounded work units that justify worker overhead. A work unit may be one item or a small related group, never the whole queue.
- Audit locally and capture the relevant changed files/checks before queueing or posting a reply.
- Outside-diff comments and nitpicks are local-only by default because they are not review threads; do not use the queue or follow-up script for them.
Reply Queue
Queue accepted stacked-review fixes before the follow-up PR exists:
python3 "$SKILL_DIR/scripts/review_reply_queue.py" add-fixed <review-item-file> \
--summary '<summary>'
After creating the new top-of-stack PR, attach the PR URL and post pending replies:
python3 "$SKILL_DIR/scripts/review_reply_queue.py" post-pending \
--source-pr <reviewed-pr-number> \
--fix-pr-url https://github.com/<owner>/<repo>/pull/<fix-pr> \
--dry-run
python3 "$SKILL_DIR/scripts/review_reply_queue.py" post-pending \
--source-pr <reviewed-pr-number> \
--fix-pr-url https://github.com/<owner>/<repo>/pull/<fix-pr>
Declined comments can use the same queue. add-declined prints a draft ID; use
that ID for immediate posting:
python3 "$SKILL_DIR/scripts/review_reply_queue.py" add-declined <review-item-file> \
--reason '<reason>'
python3 "$SKILL_DIR/scripts/review_reply_queue.py" post <declined-draft-id> --dry-run
python3 "$SKILL_DIR/scripts/review_reply_queue.py" post <declined-draft-id>
Use post_github_review_followup.py only as a direct single-item escape hatch.
Related Skills
rarestg/stacked-diffs
tools
VerifiedTrustedCommunity
Break large code changes into small, stacked pull requests using vanilla git and the gh CLI. Auto-trigger when implementing a feature or change that spans multiple logical steps, touches several files, or will exceed ~200 changed lines. Also trigger on "stack PRs", "break this into smaller PRs", "stacked diffs", or "create a PR stack". Do NOT trigger for single-file fixes, small bug fixes, or changes under ~200 lines that are a single logical unit.
1SKILL.mdUpdated Apr 12, 2026
rarestg/graphify-architecture-review
development
VerifiedTrustedCommunity
Run reusable Graphify-led architecture analysis for codebases using semantic graphs, optional subagent extraction, graph synthesis, source-search validation, graph-shape review, and follow-up refactor planning. Use when asked to analyze repo architecture, god nodes, surprising edges, topology, module boundaries, or graph-derived cleanup/refactor opportunities.
SKILL.mdUpdated May 2, 2026
rarestg/delegated-delivery
testing
VerifiedTrustedCommunity
Run a meaningful coding ticket through a delegated delivery workflow: tighten the ticket, assign one ticket owner, delegate implementation, get an independent review, scan for high-value simplification, validate the result, and return a compact outcome packet. Use when the user wants structured agent execution with clear scope, ownership, and review rather than a single-pass implementation. Triggers on: "delegate this ticket", "use a sub-PM", "run this through worker and reviewer", "own this ticket end to end", "send this for independent review", or "close this ticket out with review". Skip trivial fixes and tasks that are still too vague to delegate.
SKILL.mdUpdated Apr 18, 2026
rarestg/task-os
data-ai
VerifiedTrustedCommunity
Operating protocol that uses Taskwarrior as the continuity layer across conversations. Grounds every interaction in real task state before acting. Activate on "morning" / "briefing" for daily overview, on "status" / "what's next" for current state, when capturing tasks ("remind me to", "add task", "I need to"), when recovering from stalls, or when executing structured work across projects, repos, and life domains.
SKILL.mdUpdated Apr 12, 2026