apply-turbo-handoffs
Audit the turbo lessons /self-improve wrote to .turbo/handoff/ and apply approved ones. Use when the user asks to \"read…
Evaluate, fix, and answer GitHub PR comments, and fix what failing checks report. Use when the user asks to \"resolve PR feedback\", \"resolve PR comments\", \"answer review questions\", or \"fix PR checks\".
Claude Code
$ npx -y skills add tobihagemann/turbo --skill resolve-pr-feedback --agent claude-code
Codex
$ npx skills add tobihagemann/turbo --skill resolve-pr-feedback -a codex -y
Cursor
$ npx skills add tobihagemann/turbo --skill resolve-pr-feedback -a cursor -y
Gemini CLI
$ npx skills add tobihagemann/turbo --skill resolve-pr-feedback -a gemini-cli -y
GitHub Copilot
$ npx skills add tobihagemann/turbo --skill resolve-pr-feedback -a github-copilot -y
OpenCode
$ npx skills add tobihagemann/turbo --skill resolve-pr-feedback -a opencode -y
Windsurf
$ npx skills add tobihagemann/turbo --skill resolve-pr-feedback -a windsurf -y
name: resolve-pr-feedback description: "Evaluate, fix, and answer GitHub PR comments, and fix what failing checks report. Use when the user asks to \"resolve PR feedback\", \"resolve PR comments\", \"answer review questions\", or \"fix PR checks\"."
Fetch unresolved review comments from a GitHub PR (inline threads, review-body observations, and issue-comment observations from the PR conversation), evaluate each one, fix or skip based on confidence, answer reviewer questions using the recalled rationale behind the change, and reply. Inline threads are answered with thread replies; issue-comment findings from people are answered with new PR conversation comments. Review-body findings, AI-reviewer issue comments, and the findings behind the head commit's failing checks flow through the same evaluate-and-fix pipeline; their outcomes land only in the summary.
At the start, use `TaskCreate` to create a task for each step:
1. Fetch comments and checks 2. Triage already-addressed feedback 3. Run `/interpret-feedback` skill 4. Split questions and change requests 5. Run `/evaluate-findings` skill 6. Resolve ambiguities 7. Run `/implement-findings` skill 8. Verify fixes 9. Answer reviewer questions 10. Wait for AI re-reviews and checks 11. Run `/reply-to-pr-threads` skill 12. Run `/reply-to-pr-conversation` skill 13. Summary
Auto-detect owner, repo, and PR number from current branch if not provided. Then run `${CLAUDE_SKILL_DIR}/scripts/fetch-pr-data.sh`, which handles full pagination (reviews, review threads, inner comment pages for long threads, issue comments, commits, the head commit's checks) and emits a single merged JSON document:
bash ${CLAUDE_SKILL_DIR}/scripts/fetch-pr-data.sh <owner> <repo> <pr_number>Output shape:
{
"meta": { "title", "url", "headRefName", "headRefOid", "baseRefName", "body" },
"reviewThreads": [ { "id", "isResolved", "isOutdated", "comments": { "nodes": [ { "author", "body", "path", "line", "originalLine", "diffHunk" } ] } } ],
"reviews": [ { "author", "body", "state", "submittedAt" } ],
"issueComments": [ { "author", "body", "createdAt", "updatedAt", "url" } ],
"commits": [ { "commit": { "oid", "abbreviatedOid", "message", "committedDate" } } ],
"checks": [ { "name", "app", "state", "conclusion", "title", "detailsUrl" } ]
}Filter review threads to unresolved only. Filter reviews to those with a non-empty body, excluding `PENDING` state (unsubmitted drafts). Filter issue comments to those with a non-empty body. Filter checks to those whose `state` is `failing`.
Read what each failing check reports, by its `app`:
Tag each check finding with the source `check` and the name of its check. Check findings skip Steps 2 through 4 and feed Step 5. Record each unreadable check's name, title, and `detailsUrl` for the Step 13 summary.
Review bodies and PR conversation comments (issue comments) often pack multiple distinct concerns into one comment. Split each non-empty, non-PENDING review body and each non-empty issue comment into atomic observations, one per paragraph or bullet, so each can be evaluated on its own merits. When a review body nests observations inside collapsed `<details>` blocks, as AI reviewers do for nitpicks that name a file and line range, extract every observation inside them, keeping its file and line range in its text, and drop only blocks that carry no observation, such as review metadata, commit lists, and prompts for AI agents.
For every observation, check whether a subsequent commit already addresses it. Compare the source timestamp (`submittedAt` for review bodies, `createdAt` for issue comments) against each commit's `committedDate`; only commits after the source was posted can address it. Start with commit messages; read `git show <oid>` only when the message is ambiguous. A commit addresses an observation when its changes clearly resolve that specific concern. Touching the same area is not enough for an observation.
When an observation asserts a requirement or an intended behavior, compare that assertion against `meta.body`. The PR description is the author's own current statement of intent, so a description stating the opposite leaves a premise for Step 5 to settle. Record the contradiction against the observation and carry it forward, so Step 5 settles that premise once instead of re-deriving it for every finding the premise produced.
Classify each observation:
Review-body and issue-comment findings have no `diffHunk`, file path, or line reference unless their text names a file and line. The
A human-gated agentic software factory for Claude Code and Codex: you decide what to build and judge the result; skills shape, build, polish, ship, and learn.
Audit the turbo lessons /self-improve wrote to .turbo/handoff/ and apply approved ones. Use when the user asks to \"read…
Apply accepted review findings as code changes, escalating ambiguous ones to the user. Use when the user asks to \"apply…
Assess project-wide technical debt (hotspots, deprecated APIs, duplication, low-value tests) into a ranked report. Use when the…
Capture an out-of-scope improvement or accepted simplification in .turbo/backlog.md. Use proactively mid-task, or when the user…
Shared changelog conventions and formatting rules. Not typically invoked directly.
Enforce existence, reuse, mirror, and symmetry principles so new code stays minimal and consistent. Use when writing, changing,…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.