apply-findings SKILL.md skillA

apply-findings from tobihagemann/turbo is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

mdr add tobihagemann/turbo/apply-findings@git:20261023.44fa179

Pins git:20261023.44fa179 in mdr.lock. Pin the fingerprint instead.

Audit grade

A, 17 of 17 checks passed

Kind

SKILL.md skill

Repository

tobihagemann/turbo

Path

codex/skills/apply-findings/SKILL.md

Versions recorded

17

Latest version

git:20261023.44fa179, committed Oct 23, 2026

First version recorded

Aug 8, 2026

Size

11,863 bytes

Repository stars

417

License

MIT

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".

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Apply Findings

Apply evaluated findings from the conversation context. Findings must have been through `$evaluate-findings` first.

## Step 1: Identify Findings

Collect all findings from the conversation context. Findings should have Verdict columns (Apply, Skip, Escalate) from `$evaluate-findings`.

If findings are unevaluated (raw output without verdicts), stop and say to run `$evaluate-findings` first.

## Step 2: Apply in File Order

Group Apply findings by file path and apply in file order to minimize context switching. For each finding:

1. Read the full function or logical block at the referenced location
2. Verify the finding still applies to the current code
3. Before applying a fix that stops a failure, whether the finding suggested it or you derived it, confirm the fix makes the failure the finding describes unreachable rather than only defeating the finding's reproduction: construct an input that clears the point the fix guards, trace whether it still reaches that failure further along, and write any regression test the fix adds from that input. When the fix encodes, escapes, quotes, or otherwise sanitizes untrusted input, construct such inputs from every character
…

Read the whole file at its exact version.

How to install

mdr add tobihagemann/turbo/apply-findings@sha256:310fb670a69268ba

[![mdr](https://markdownregistry.com/badge/art_eh3b2ag2jaajgh5k.svg)](https://markdownregistry.com/a/art_eh3b2ag2jaajgh5k)

Versions

The registry has recorded 17 versions of this file, between Aug 8, 2026 and Oct 23, 2026, about one every 5 days.

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_eh3b2ag2jaajgh5k
GET https://markdownregistry.com/api/v1/resolve?ref=tobihagemann/turbo/apply-findings
GET https://markdownregistry.com/api/v1/blob/310fb670a69268ba57bb78fdec8fc767b31352017564ba82974519037094f21c

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from tobihagemann/turbo

Every file in tobihagemann/turbo

Other files named apply-findings

Browse by kind, by grade A, or by owner.