skills/review-all-prs/SKILL.md
Dispatch parallel agents to address review comments on all open PRs. Each agent fixes code, replies inline, resolves threads, and reports what needs human input. Use when user says '/review-all-prs', 'fix all PR reviews', 'address all reviews', or when /scrum shows PRs with pending reviews.
npx skillsauth add razbakov/skills review-all-prsInstall 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.
Dispatch one agent per PR to address review comments. Agents fix what they can autonomously. Human gets a summary of what needs decisions.
For each project in ~/Projects/ that has open PRs:
cd ~/Projects/PROJECT
REPO=$(gh repo view --json nameWithOwner --jq '.nameWithOwner')
gh pr list --state open --json number,title,url,headRefName
For each PR, check for unresolved threads:
gh api graphql -f query='
query {
repository(owner: "OWNER", name: "REPO") {
pullRequest(number: NUMBER) {
reviewThreads(first: 50) {
nodes { isResolved }
}
}
}
}' --jq '[.data.repository.pullRequest.reviewThreads.nodes[] | select(.isResolved == false)] | length'
Skip PRs with 0 unresolved threads.
For each PR with unresolved threads, dispatch using the /inbox pattern:
pr-review-${PR_NUMBER}~/Tasks/${PROJECT}-pr-review-${PR_NUMBER}The worktree setup is different from normal /inbox — we need the PR branch, not a new branch:
TASK_DIR=~/Tasks/${PROJECT}-pr-review-${PR_NUMBER}
git -C ~/Projects/${PROJECT} worktree add ${TASK_DIR} ${PR_BRANCH}
Each agent gets this prompt:
# Address PR review comments for PR #NUMBER
**Repo:** OWNER/REPO
**PR:** #NUMBER — TITLE
**Branch:** BRANCH
**URL:** PR_URL
## Instructions
You are addressing review comments on this PR. Follow the pr-review-responder workflow:
1. Fetch all inline review comments:
`gh api repos/OWNER/REPO/pulls/NUMBER/comments --jq '.[] | {id, path, line, body}'`
2. Categorize each comment:
- **Code fix needed** → Fix the code, commit with SHA reference
- **Acknowledged (missing feature)** → Create a GitHub issue, reply with link
- **Acknowledged (product decision)** → DO NOT fix or create issue. Write to NEEDS_INPUT file instead.
- **By design** → Reply with reasoning
- **Already fixed** → Reply noting the commit
3. Fix all code issues, then verify:
```bash
bun run build 2>&1 || npm run build 2>&1 || true
Commit and push:
git add -A && git commit -m "Address PR #NUMBER review feedback" && git push
Reply to each comment inline:
gh api -X POST repos/OWNER/REPO/pulls/NUMBER/comments -f body="Fixed in SHA" -F in_reply_to=COMMENT_ID
Resolve threads via GraphQL (get thread IDs first, then resolveReviewThread mutation)
For items needing human input, append to ${TASK_DIR}/needs-input.md:
## PR #NUMBER — TITLE
- [ ] Comment ID XXXX: <summary of what needs deciding>
### 4. Launch all agents in parallel
Use the standard `/inbox` tmux launch pattern for each PR. Session name: `wf-pr-review-${PR_NUMBER}`.
### 5. Report dispatch summary
After dispatching all agents, output:
Dispatched N agents to address PR reviews:
Run /scrum to check progress.
## Collecting Results
When agents finish (check via `/scrum`), collect results:
```bash
# Check for needs-input files across all review agents
for dir in ~/Tasks/*-pr-review-*/; do
if [ -f "$dir/needs-input.md" ]; then
echo "=== $(basename $dir) ==="
cat "$dir/needs-input.md"
fi
done
Present to user:
## Review Results
### Fully resolved (ready to test)
- PR #23: Add hero image — all 3 threads fixed and resolved
- PR #24: Wire useDinners — all 2 threads fixed and resolved
### Needs your input
- PR #26: Signup form
- [ ] Should email validation use regex or API check?
- [ ] Password requirements: min 8 chars or min 12?
### Failed (check logs)
- PR #27: Agent crashed — `tail ~/Tasks/project-pr-review-27/agent.log`
development
Seed a new or empty Instagram account with a 9-post grid (3×3) so the profile looks established the moment a new visitor lands. Designed for festivals, new businesses, product launches, conferences, communities — any time an empty IG profile would hurt conversion from external traffic (QR scans, flyer drops, cross-promo). Generates assets via /image-from-gemini (per content-publishing rules — never HTML), writes captions with hashtag sets, and outputs a posting order + cadence plan. Trigger generously: phrases like '9 posts for instagram', 'fill my IG', 'starter grid', 'launch grid', 'instagram seed', '9-post grid', 'IG account not to look empty', 'first instagram posts', 'feed bootstrap', '3x3 grid', 'instagram launch content'. Even if the user mentions only one piece (just the images, just the captions, just the order), use this skill — the grid only works as an integrated bundle.
testing
Translate one English blog post into multiple target languages via parallel sub-agents, preserving frontmatter conventions, hero image, and brand voice. Use when the user shares a published English post URL or markdown path and says 'translate it', 'add other languages', 'publish in DE/ES/RU/UK', 'translate to 5 languages', or asks for localized versions of a specific post.
development
Build a complete press kit for an event, product launch, or campaign — in multiple languages — and publish it as a shareable Google Drive folder ready to send to journalists, partners, or a delegate. Produces press releases (typically DE/EN/ES, or configurable), uploads press photos and flyers, creates an Overview document for at-a-glance briefing, and creates a Handover document with pending tasks, contacts, risks, and decisions so press distribution can be delegated. Use when the user says 'I need a press release', 'create a press kit', 'press release in X languages', 'set up a Drive folder for press', 'handover doc for someone else to run press', or has an upcoming announcement that needs to be sent to media. Trigger generously: even partial requests (just a press release, just a flyer folder) typically evolve into the full kit.
development
Track ticket sales for a live event (concert, festival, conference, workshop) with daily snapshots, generate a burndown chart comparing actual sales to ideal-linear targets and tier-cumulative milestones, and report whether the event is on pace. Use when the user asks how sales are going, wants to know if their event will sell out, asks for a daily sales report, wants to set up sales tracking for an upcoming event, or asks about ticket pace / velocity / projection. Trigger generously: phrases like 'how is concert sales going', 'burndown for my event', 'are we going to sell out', 'sales velocity', 'daily ticket chart', 'how many tickets do we need to sell', or any case where the user has a ticketed event with a fixed sales window and wants visibility on pacing.