fix-findings SKILL.md skillA
fix-findings from chrislacey89/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add chrislacey89/skills/fix-findings@git:20261020.df69d53Pins git:20261020.df69d53 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- chrislacey89/skills
- Path
fix-findings/SKILL.md- Versions recorded
- 11
- Latest version
- git:20261020.df69d53, committed Oct 20, 2026
- First version recorded
- Sep 4, 2026
- Size
- 36,594 bytes
- Repository stars
- 4
- License
- MIT
Invoked helper skill for fixing the /pre-merge findings a human has already chosen, with a fresh sub-agent writing each fix and a second fresh sub-agent trying to break it. Enter from the /pre-merge next-step menu option "Fix a finding on this branch first" or by typing /fix-findings <numbers>; never self-trigger without finding numbers the human picked. Not for choosing which findings to act on, not for stamping review currency, and not for merging.
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
# Fix Findings
!`PROJECT_DIR="${CLAUDE_PROJECT_DIR:-$(git rev-parse --show-toplevel)}" && mkdir -p "$PROJECT_DIR/.claude" && touch "$PROJECT_DIR/.claude/.fix-findings-active" && echo "fix-findings marker created at $PROJECT_DIR/.claude/.fix-findings-active — post-review edit lock open for this run"`
Take the review findings a human has already chosen, have a **fresh** sub-agent
write each fix, have a **second** fresh sub-agent try to break it, and report
both back. Hand off to a `/pre-merge` re-run, which is the only thing that
re-stamps.
## Why this skill exists
`/pre-merge` delegates the review to a sub-agent that did not write the code,
because the session that wrote it has already demonstrated it cannot see these
particular defects. Then the human picks findings, and the pipeline hands the
*fix* back to that same blind session. The responsive commit is the most
defect-dense code on the branch and the one commit with no independent reader.
Cohen's rule is that an author's job is to *annotate for* a reviewer, not to be
one. This skill applies it one link later: the fix's author must not be its only
…Read the whole file at its exact version.
How to install
mdr add chrislacey89/skills/fix-findings@sha256:846f4596c912da09The line at the top of this page pins the label git:20261020.df69d53, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_zsq3xwzrynmv5rzv)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 11 versions of this file, between Sep 4, 2026 and Oct 20, 2026, about one every 5 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261020.df69d53 latest | 2026-10-20 | df69d53 | 36,594 B | A | view · diff |
| git:20261020.803e4b9 | 2026-10-20 | 803e4b9 | 36,405 B | A | view · diff |
| git:20261018.026d760 | 2026-10-18 | 026d760 | 36,005 B | A | view · diff |
| git:20261018.0fb326b | 2026-10-18 | 0fb326b | 35,822 B | A | view · diff |
| git:20260917.2c12eca | 2026-09-17 | 2c12eca | 35,560 B | A | view · diff |
| git:20260910.364c2a3 | 2026-09-10 | 364c2a3 | 35,531 B | A | view · diff |
| git:20260909.a933431 | 2026-09-09 | a933431 | 33,258 B | A | view · diff |
| git:20260905.38da5c7 | 2026-09-05 | 38da5c7 | 33,132 B | A | view · diff |
| git:20260904.43f3b88 | 2026-09-04 | 43f3b88 | 31,540 B | A | view · diff |
| git:20260904.a5d19ab | 2026-09-04 | a5d19ab | 26,796 B | A | view · diff |
| git:20260904.5adb1ae | 2026-09-04 | 5adb1ae | 21,540 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (36594 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
chrislacey89/skills · 4 stars · license MIT · pushed 2026-10-22 · branch prod
API
GET https://markdownregistry.com/api/v1/artifacts/art_zsq3xwzrynmv5rzv GET https://markdownregistry.com/api/v1/resolve?ref=chrislacey89/skills/fix-findings GET https://markdownregistry.com/api/v1/blob/846f4596c912da09b6ddb1224ad77e5b1e7e148290e8a75590efd80efa43be75
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 chrislacey89/skills
Every file in chrislacey89/skills