tobihagemann/resolve-findings
codex/skills/resolve-findings/SKILL.md
Choose an implementation path (direct or plan) for evaluated findings and dispatch it. Direct path applies fixes directly; plan path runs $turboplan. Use after $evaluate-findings has tagged findings and they need to be implemented, or when the user asks to "resolve findings", "apply evaluated findings", or "dispatch findings to implementation".
$ install --global
skillsauthnpx skillsauth add tobihagemann/turbo resolve-findingsInstall 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: Jul 22, 2026, 4:53 AM216.2s3 files scanned
SKILL.md
- name:
- resolve-findings
- description:
- Choose an implementation path (direct or plan) for evaluated findings and dispatch it. Direct path applies fixes directly; plan path runs $turboplan. Use after $evaluate-findings has tagged findings and they need to be implemented, or when the user asks to \"resolve findings\", \"apply evaluated findings\", or \"dispatch findings to implementation\".
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 update_plan to track each step, restating any remaining steps of a parent workflow alongside them:
- Choose path
- 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 request_user_input to let the user choose:
- Plan — Run
$turboplanfor drafting, refinement, approval, implementation, and finalize - Direct — Run
$apply-findings, then$finalize
Suggest Plan when findings include complex or architectural changes. Suggest Direct when all findings are mechanical fixes.
Step 2: Run the Chosen Path
Read the reference file for the confirmed path and follow its phases:
- Direct path — references/direct-path.md
- Plan path — references/plan-path.md
State the chosen path before continuing with the reference file.
Then call update_plan to mark this step completed and continue with the next step of the active workflow.
Related Skills
tobihagemann/user-experience
development
VerifiedTrustedCommunity
Apply a UX lens to a user-facing change: whether it serves the user's real goal and whether the path through it holds together, using the Understanding, Bridging, and Flowing contexts. Use when scoping, planning, or assessing any change that affects what a user sees or does. Loaded as a lens during planning and assessment.
377SKILL.mdUpdated Jun 18, 2026
tobihagemann/user-experience
development
VerifiedTrustedCommunity
Apply a UX lens to a user-facing change: whether it serves the user's real goal and whether the path through it holds together, using the Understanding, Bridging, and Flowing contexts. Use when scoping, planning, or assessing any change that affects what a user sees or does. Loaded as a lens during planning and assessment.
377SKILL.mdUpdated Jun 18, 2026
tobihagemann/assess-technical-debt
development
VerifiedTrustedCommunity
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.
377SKILL.mdUpdated Jun 15, 2026
tobihagemann/simplify-docs
development
VerifiedTrustedCommunity
Run a multi-agent review of code comments and markdown documentation for unnecessary content, then fix the issues. Covers what-restating comments, name-mirroring doc comments, status-update prose, and other documentation noise. Use when the user asks to "simplify docs", "simplify documentation", "clean up comments", "clean up docs", "review documentation", "strip unnecessary comments", "reduce doc noise", or "run simplify-docs".
377SKILL.mdUpdated May 15, 2026