Agent skill

Resolve Findings

Implement evaluated findings: load code-style rules, apply the accepted fixes, then close out the change with full or quick QA.

MITAuto-check passedWriting & Content

Install Resolve Findings

skills CLI

$ npx skills add tobihagemann/turbo --skill resolve-findings -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install tobihagemann/turbo resolve-findings --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/claude/skills/resolve-findings .claude/skills/resolve-findings && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "resolve-findings" agent skill from https://github.com/tobihagemann/turbo/tree/main/claude/skills/resolve-findings into .claude/skills/resolve-findings/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resolve-findings", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/tobihagemann/turbo/tree/main/claude/skills/resolve-findings

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add tobihagemann/turbo --skill resolve-findings -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install tobihagemann/turbo resolve-findings --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .agents/skills && cp -r skills-src/claude/skills/resolve-findings .agents/skills/resolve-findings && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "resolve-findings" agent skill from https://github.com/tobihagemann/turbo/tree/main/claude/skills/resolve-findings into .agents/skills/resolve-findings/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resolve-findings", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add tobihagemann/turbo --skill resolve-findings -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install tobihagemann/turbo resolve-findings --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/claude/skills/resolve-findings .cursor/skills/resolve-findings && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "resolve-findings" agent skill from https://github.com/tobihagemann/turbo/tree/main/claude/skills/resolve-findings into .cursor/skills/resolve-findings/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resolve-findings", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/tobihagemann/turbo.git --path claude/skills/resolve-findings

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add tobihagemann/turbo --skill resolve-findings -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install tobihagemann/turbo resolve-findings --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/claude/skills/resolve-findings .gemini/skills/resolve-findings && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "resolve-findings" agent skill from https://github.com/tobihagemann/turbo/tree/main/claude/skills/resolve-findings into .gemini/skills/resolve-findings/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resolve-findings", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install tobihagemann/turbo resolve-findings

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add tobihagemann/turbo --skill resolve-findings -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .github/skills && cp -r skills-src/claude/skills/resolve-findings .github/skills/resolve-findings && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "resolve-findings" agent skill from https://github.com/tobihagemann/turbo/tree/main/claude/skills/resolve-findings into .github/skills/resolve-findings/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resolve-findings", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add tobihagemann/turbo --skill resolve-findings -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install tobihagemann/turbo resolve-findings --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/claude/skills/resolve-findings .opencode/skills/resolve-findings && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "resolve-findings" agent skill from https://github.com/tobihagemann/turbo/tree/main/claude/skills/resolve-findings into .opencode/skills/resolve-findings/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "resolve-findings", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: resolve-findings
GitHub stars: 408
Token cost: ~286 tokens
SKILL.md length: 116 words
Files: 1
Skills in repo: 81
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Implement evaluated findings: load code-style rules, apply the accepted fixes, then close out the change with full or quick QA.

Works in 3 steps: Run /code-style Skill → Run /apply-findings Skill → Close Out the Change
Asks to resolve findings
SKILL.md covers Task Tracking, Step 1: Run /code-style Skill, Step 2: Run /apply-findings… and Step 3: Close Out the Change
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Resolve Findings is an agent skill from tobihagemann/turbo. Implement evaluated findings: load code-style rules, apply the accepted fixes, then close out the change with full or quick QA. 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".

Its SKILL.md is about 290 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Writing & Content, covering Plain language and style rules. The repository describes itself as: Reusable workflows for planning, building, reviewing, and shipping with Claude Code and Codex. The licence is MIT.

When your agent uses it

Asks to resolve findings
Apply evaluated findings
Dispatch findings to implementation

Example prompts

“resolve findings”
“apply evaluated findings”
“dispatch findings to implementation”
“/resolve-findings”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

Run /code-style Skill
Run /apply-findings Skill
Close Out the Change

What it can do on your machine

Read from SKILL.md and the folder at commit 931eda5. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Resolve Findings loads about 286 tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 116 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~85
When it runs · the whole SKILL.md, loaded when a task matches: ~286

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from tobihagemann/turbo at commit 931eda5, republished under its MIT licence (© tobihagemann). 116 words, ~286 tokens.

Download SKILL.mdSave it as .claude/skills/resolve-findings/SKILL.md (or your agent's skills folder).

name: resolve-findings
description: Implement evaluated findings: load code-style rules, apply the accepted fixes, then close out the change with full or quick QA. 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

Apply evaluated findings and close out the change.

Task Tracking

At the start, use TaskCreate to create a task for each step:

Run /code-style skill
Run /apply-findings skill
Close out the change

Step 1: Run `/code-style` Skill

Run the /code-style skill to load existence, reuse, mirror, and symmetry rules before editing.

Step 2: Run `/apply-findings` Skill

Run the /apply-findings skill on the evaluated findings.

Step 3: Close Out the Change

If no changes were made, skip this step.

Use AskUserQuestion to choose how to close out the change:

Full QA — run the /finalize skill
Quick close — run the /quick-finalize skill

Then use the TaskList tool and proceed to any remaining task.

Files

Just SKILL.md in claude/skills/resolve-findings of tobihagemann/turbo.

Open the folder on GitHubat commit 931eda5

Compare with similar skills

Resolve Findings next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Resolve Findings compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Resolve Findings this skilltobihagemann/turbo	408	—	~286	Automated safety check: Pass	MIT	2 days ago
Asd Ste100danyuchn/asd-ste100-skill	4.3k	—	~4.1k	Automated safety check: Pass	MIT	7 days ago
Technical Writing Standardcursor/plugins	11k	10 repos	~2.3k	Automated safety check: Pass	None	today
Ponytail AuditDietrichGebert/ponytail	160k	—	~1.4k	Automated safety check: Pass	MIT	yesterday
Natural Japanese Business Writingcoji/natural-japanese	1.9k	—	~2.1k	Automated safety check: Pass	MIT	1 mo ago
PgjevrealZachi/pg-jev	1.1k	—	~2.9k	Automated safety check: Pass	Custom licence	5 days ago

Similar skills

Asd Ste100
danyuchn/asd-ste100-skill
A skill your agent uses when English text must be parsed without a human to resolve ambiguity — tool descriptions, error messages, inter-agent instructions, system prompts, status reports — and…
4.3k GitHub stars~4.1k tokensUpdated 7 days ago
Writing & ContentAuto-check passed
Technical Writing Standard
cursor/plugins
Official
Applies four layers of technical-writing rules to docs, RFCs, readmes, PR descriptions and commit messages so a tired engineer follows them on the first read.
11k GitHub starsUsed in 10 repos~2.3k tokens
Writing & ContentAuto-check passed
Ponytail Audit
DietrichGebert/ponytail
Quality audit of a whole repo: bugs, security holes, what breaks under real load, risky code without tests, slow paths, and what to delete, merge or split.
160k GitHub stars~1.4k tokensUpdated yesterday
Writing & ContentAuto-check passed
Natural Japanese Business Writing
coji/natural-japanese
Writes and edits Japanese business documents so they read clearly and naturally, removes AI-sounding phrasing and can score how AI-like a text reads.
1.9k GitHub stars~2.1k tokensUpdated 1 mo ago
Writing & ContentAuto-check passed
Pgjev
realZachi/pg-jev
Install, configure, query and explain pgjev (the jev PostgreSQL extension that filters, ranks and classifies rows with plain-language conditions via TypeSafe's Jev model).
1.1k GitHub stars~2.9k tokensUpdated 5 days ago
Writing & ContentAuto-check passed
Defensive Writing Editor
lennney/stop-that-shit
Cuts defensive disclaimers, stacked hedging and self-protective narration from proposals and summaries, keeping only limits that affect the reader's decision.
2.5k GitHub starsUsed in 1 repo~1.2k tokens
Writing & ContentAuto-check passed

Questions about Resolve Findings

What does Resolve Findings do?

Implement evaluated findings: load code-style rules, apply the accepted fixes, then close out the change with full or quick QA. Resolve Findings is an agent skill from tobihagemann/turbo. Implement evaluated findings: load code-style rules, apply the accepted fixes, then close out the change with full or quick QA.

When should I use Resolve Findings?

Resolve Findings fits situations like: asks to resolve findings; apply evaluated findings; dispatch findings to implementation.

How do I install Resolve Findings in Claude Code?

Run `npx skills add tobihagemann/turbo --skill resolve-findings -a claude-code`. Or copy the skill folder (claude/skills/resolve-findings in tobihagemann/turbo) into .claude/skills/resolve-findings in your project. Claude Code loads it when a task matches its description.

How do I install Resolve Findings in Codex?

Run `npx skills add tobihagemann/turbo --skill resolve-findings -a codex`. Or copy the skill folder (claude/skills/resolve-findings in tobihagemann/turbo) into .agents/skills/resolve-findings in your project. Codex loads it when a task matches its description.

Can I use Resolve Findings in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tobihagemann/turbo --skill resolve-findings -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/resolve-findings, .gemini/skills/resolve-findings, .github/skills/resolve-findings and .opencode/skills/resolve-findings in your project.

What does Resolve Findings need to run?

SKILL.md names no scripts, command-line tools or credentials: Resolve Findings is instructions for the agent only.

Does Resolve Findings access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Resolve Findings safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Resolve Findings use?

Resolve Findings is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Resolve Findings use?

About 286 tokens (SKILL.md is roughly 1.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Resolve Findings?

Skills that share tags, products or a category with Resolve Findings: Asd Ste100 (danyuchn/asd-ste100-skill, 4.3k stars), Technical Writing Standard (cursor/plugins, 11k stars), Ponytail Audit (DietrichGebert/ponytail, 160k stars) and Natural Japanese Business Writing (coji/natural-japanese, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Resolve Findings?

tobihagemann (a GitHub user) maintains it in tobihagemann/turbo, which has 408 GitHub stars. The repository holds 81 skills in this directory. The repository was last updated on October 9, 2026.

Source: tobihagemann/turbo on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Resolve Findings

Install Resolve Findings

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Resolve Findings

Task Tracking

Step 1: Run `/code-style` Skill

Step 2: Run `/apply-findings` Skill

Step 3: Close Out the Change

Files

Compare with similar skills

Similar skills

Asd Ste100

Technical Writing Standard

Ponytail Audit

Natural Japanese Business Writing

Pgjev

Defensive Writing Editor

More from tobihagemann/turbo

Consult Oracle

Fetch PR Comments

Recall Rationale

Resolve PR Comments

Resolve PR Comments

Assess Technical Debt

Questions about Resolve Findings

Install Resolve Findings

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Resolve Findings

Task Tracking

Step 1: Run /code-style Skill

Step 2: Run /apply-findings Skill

Step 3: Close Out the Change

Files

Compare with similar skills

Similar skills

More from tobihagemann/turbo

Related

Questions about Resolve Findings

Step 1: Run `/code-style` Skill

Step 2: Run `/apply-findings` Skill