repair
Skill0 starsChanged 9 days agoMITView on GitHub
Apply owner-approved fixes from a second brain lint report, one item at a time, with logging. Use when the owner says "fix 1-3", "repair the lint findings", "merge these duplicate pages", "fix the broken links", or approves items from a report in 50-outputs/lint/.
8 other projects use a version of this.
Adopted by
Most recently taken up by
- ohanyan/adultingtheir own version, first seen Nov 16, 2026
- mlflow/mlflowtheir own version, first seen Nov 15, 2026
- tygwan/cc-initializer-windowstheir own version, first seen Oct 20, 2026
- xiaolai/cc-suitetheir own version, first seen Oct 19, 2026
- lifebugz/cc-mermaidtheir own version, first seen Oct 15, 2026
- dynos-fit/dynos-worktheir own version, first seen Oct 13, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- mlflow/mlflow★ 29ksame name
- xiaolai/cc-suite★ 56same name
- dynos-fit/dynos-work★ 2same name
- ohanyan/adulting★ 1same name
- lifebugz/cc-mermaid★ 0same name
- tygwan/cc-initializer★ 0same name
- tygwan/cc-initializer-windows★ 0same name
- yuanhaorannnnnn/agent-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- brain-reviewSkill
- captureSkill
- gap-finderSkill
- ingestSkill
- lintSkill
- projectSkill
- querySkill
- second-brainSkill
- setupSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 1 is distinctive, and 5 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Only fix what the owner approved.
- Distinctive: line 13
Read every page involved before editing.
- Very specific: line 16
Run python3 scripts/lint.py and confirm the fixed items are gone and nothing new broke.
- Very specific: line 18
Run scripts/qmd-sync.sh (renames and deprecations must reach the search index).
- Very specific: line 36
Use git mv old new, then update every inbound link: grep -rl "\[\[old-name" --include=*.md .
- Very specific: line 41
Never delete pages: deprecate.
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Repair: apply approved lint fixes
Only fix what the owner approved. Use the latest report in 50-outputs/lint/ unless told otherwise.
Steps
- Open the report; list the approved items back in one line each ("Fixing: 1) broken link …, 2) …").
- For each item, in order:
- Read every page involved before editing.
- Apply the smallest fix that resolves it (patterns below).
- Note what you did next to the item in the report:
✔ fixed: <how>(or✘ skipped: <why>).
- Run
python3 scripts/lint.pyand confirm the fixed items are gone and nothing new broke. - Append to
log.md:## [YYYY-MM-DD] repair | items 1-3 from YYYY-MM-DD-lintwith created/updated pages. - Run
scripts/qmd-sync.sh(renames and deprecations must reach the search index). - Suggest a commit:
git commit -am "repair: <summary>".
Fix patterns
| Finding | Fix |
| broken-link | Fix the typo, or create a seed page for the target (frontmatter, one-line summary, link back) |
| not in index | Add the index.md line |
| frontmatter | Add the missing fields; never invent sources. Downgrade to seed if there are none |
| orphan | Link it from 1-2 genuinely related pages (with a reason), or propose deprecation |
| one-way-link | Add the back-reference with a short "why" in ## Related |
| duplicate | Merge: pick the canonical page (more links/content), move unique content + sources into it, add the other's title to aliases, set the other to status: deprecated + superseded_by: "[[canonical]]", repoint inbound links |
| stale-state | Re-check sources; update with a new as-of date, or mark "(unverified since YYYY-MM-DD)" |
| stale-seed | Grow from existing sources, merge, or deprecate (ask which) |
| contradiction | Add a ## Contradictions section; don't pick a winner unless a newer/stronger source settles it |
| raw-modified | Don't touch. Tell the owner: git checkout -- <file> restores it |
Renames and moves
Use git mv old new, then update every inbound link: grep -rl "\[\[old-name" --include=*.md . → edit each.
Rename = check in with the owner first (AGENTS.md §6 rule 7).
Hard constraints
- One approved item at a time; anything beyond the approved list goes back to the owner.
- Never delete pages: deprecate. Never edit
10-raw/or40-journal/. - More than 5 files affected by one item → show the plan and wait.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

