resolve-findings
The resolve-findings skill categorizes evaluated findings by complexity and guides users to choose between two implementation approaches: a direct path that applies fixes immediately via /apply-findings, or a plan path that uses /turboplan for structured drafting and refinement. Use this skill after /evaluate-findings has tagged findings ready for implementation or when users request to resolve, apply, or dispatch findings.
git clone --depth 1 https://github.com/tobihagemann/turbo /tmp/resolve-findings && cp -r /tmp/resolve-findings/claude/skills/resolve-findings ~/.claude/skills/resolve-findingsSKILL.md
# Resolve Findings Choose a path for evaluated findings and run it. Direct path applies fixes directly; plan path runs `/turboplan`. ## Task Tracking At the start, use `TaskCreate` to create a task for each step: 1. Choose path 2. Run the chosen path ## Step 1: Choose Path Present a summary of accepted findings (Apply verdict): count by complexity (mechanical fixes vs. architectural or design changes). Then use `AskUserQuestion` to let the user choose: - **Plan** — Run `/turboplan` for drafting, refinement, approval, implementation, and finalize - **Direct** — Run `/apply-findings`, then close out the change Suggest Plan when findings include complex or architectural changes. Suggest Direct when all findings are mechanical fixes. Add a **Get a second opinion** option whenever the findings would establish a pattern others will follow, change an interface, or commit to a data shape, and whenever neither path earns the suggestion with conviction. It runs the `/consult-codex` skill for which path the findings warrant on technical merit. Then resolve the path with that answer in hand, re-asking when the choice stays the user's. ## Step 2: Run the Chosen Path Read the reference file for the confirmed path and follow its phases: - **Direct path** — [references/direct-path.md](references/direct-path.md) - **Plan path** — [references/plan-path.md](references/plan-path.md) State the chosen path before continuing with the reference file. Then use the TaskList tool and proceed to any remaining task.
For each reviewer question on a PR, recall implementation reasoning and compose a raw answer. Use when the user asks to \"answer reviewer questions\", \"draft answers to PR questions\", or \"explain reviewer questions\".
Apply findings by making the suggested code changes. Applies accepted verdicts, escalates ambiguous findings to the user, and offers to note genuine improvements for later. Use when the user asks to \"apply findings\", \"apply fixes\", \"apply suggestions\", \"apply accepted findings\", \"fix the findings\", or \"apply the review results\".
Assess project-wide structural technical debt: complexity hotspots, deprecated API usage, duplication clusters, and architecture rot. Ranks findings by impact and refactor effort into a report at .turbo/technical-debt.md. Use when the user asks to \"assess technical debt\", \"find technical debt\", \"review technical debt\", \"what should we refactor\", \"find refactoring candidates\", \"where is the code rot\", or \"what's our worst code\". Analysis-only — does not modify code.
Project-wide health audit pipeline that fans out to all analysis skills in parallel, evaluates findings, and produces a unified report at .turbo/audit.md. Use when the user asks to \"audit the project\", \"run a full audit\", \"project health check\", \"audit my code\", \"codebase audit\", or \"comprehensive review\".
Shared changelog conventions and formatting rules referenced by $create-changelog and $update-changelog. Not typically invoked directly.
Run a non-interactive Claude Code print-mode call from Codex. Use when the user asks to \"claude print\", \"ask claude\", \"run claude\", \"consult claude\", or when a Codex Turbo skill needs Claude as an independent peer reviewer.
Enforce existence, reuse, mirror, and symmetry principles to keep new code minimal and consistent with surrounding code. Use when writing new code in an existing codebase, adding new features, refactoring, or making any code changes.
Run autonomous task execution using the codex CLI. Use when the user asks to \"codex exec\", \"run codex exec\", \"execute a task with codex\", or \"delegate to codex\".