repo-doctor
Skill1 starsChanged 42 days agoMITView on GitHub
Read-only health check for this workspace. Use before committing changes under skills/, hooks/, .claude/, or .codex/, when validating skills/hooks/memory consistency, or when the user asks "valida o repo", "checa as skills", "tem ref quebrada?", "algum binário grande?", "repo lint", "repo-doctor". Verifies stage aliases, memory skeleton, real path references, large files (working tree + git history), hooks cited in docs, skill frontmatter, and tracked-vs-ignored local artifacts. Reports findings only — never edits, deletes, or touches the remote.
- Commits and pushes
1 other project uses a version of this.
Adopted by
Most recently taken up by
- ieeecsopen/mcp-cstheir own version, first seen Aug 27, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- ieeecsopen/mcp-cs★ 3same 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 repository65 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- anti-slopSkill
- data-science-analystSkill
- humanize-deliverablesSkill
- humanizerSkill
- inference-disciplineSkill
- pm-archetype-aiSkill
- pm-archetype-enterpriseSkill
- pm-archetype-growthSkill
- pm-archetype-platformSkill
- pm-phase-defineSkill
- pm-phase-deliverSkill
- pm-phase-developSkill
- pm-phase-discoverSkill
- pm-prioritization-regua-comumSkill
- pm-product-senseSkill
- pm-storytellingSkill
- pm-transversal-analysisSkill
- pm-transversal-commsSkill
- pm-transversal-docsSkill
- pm-transversal-stakeholderSkill
- anti-slopSkill
- data-science-analystSkill
- humanize-deliverablesSkill
- humanizerSkill
- inference-disciplineSkill
- pm-archetype-aiSkill
- pm-archetype-enterpriseSkill
- pm-archetype-growthSkill
- pm-archetype-platformSkill
- pm-phase-defineSkill
- pm-phase-deliverSkill
- pm-phase-developSkill
- pm-phase-discoverSkill
- pm-prioritization-regua-comumSkill
- pm-product-senseSkill
- pm-storytellingSkill
- pm-transversal-analysisSkill
- pm-transversal-commsSkill
- pm-transversal-docsSkill
- pm-transversal-stakeholderSkill
- repo-doctorSkill
- umbertoSkill
- anti-slopSkill
- data-science-analystSkill
- humanize-deliverablesSkill
- humanizerSkill
- inference-disciplineSkill
- pm-archetype-aiSkill
- pm-archetype-enterpriseSkill
- pm-archetype-growthSkill
- pm-archetype-platformSkill
- pm-phase-defineSkill
- pm-phase-deliverSkill
- pm-phase-developSkill
- pm-phase-discoverSkill
- pm-prioritization-regua-comumSkill
- pm-product-senseSkill
- pm-storytellingSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Read-only consistency check for this PM workspace.
- Distinctive: line 12
Run each from the repo root.
- Very specific: line 26
Read-only. Never Edit/Write/rm, never git push/filter-repo/rebase, never delete memory.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
repo-doctor
Read-only consistency check for this PM workspace. Run the checks below, then emit the findings table. Never edit, delete, or run anything that touches the git remote.
Checks
Run each from the repo root. Treat any surprising result as a finding.
- Stage schema —
python3 scripts/validate_context.py(exit 0 = ok) andpython3 scripts/advance_stage.py --list. Confirmactive-context.mdresolves to a canonical stage; flag a rawdiscoverthat is not being aliased todiscovery. 1b. Memory caps —python3 scripts/memory.py doctor(exit 0 = ok). Flags: pointer over 2 KB, more or fewer than one ACTIVE block, missingCurrent stage:, parked slugs without aprojects/dir orstate.md, changelogs holding more than 3 entries, warm files (changelog.md,session-kickoff.md,state.md,profile.md,decisions.md,insights.md) and the shared org files (.ai/memory/org/*.md) over their soft caps (distill candidates, or prose to trim), pending.distill/packages, a stale archive index (runmemory.py index <slug>), and PII-named project dirs the scripts skip. It also warns on e-mail and phone patterns inside.ai/memory/org/*.md: a role alias is fine, a person is not, and a name is a review rule no pattern catches. - Memory skeleton versioned —
git status --short --ignored .ai/memoryshould show_templates/*andactive-context.example.mdas versionable while real memory stays ignored. Confirm withgit check-ignore -v .ai/memory/active-context.md .ai/memory/projects .ai/memory/inbox.md .ai/memory/index.md .ai/memory/org(no real memory leaking into git;.ai/memory/orgis ignored upstream and un-ignored only in a fork). - Real path references — for each
references/...mdor sibling-relative../<skill>/...mdpath mentioned in anySKILL.mdunderskills/, confirm the target file exists relative to the file that cites it (not a fixed depth — aSKILL.mdand areferences/*.mdfile resolve../differently). Resolve the path before flagging (a sibling skill'sreferences/dir is valid). This is the corrected check: do not flag a skill just because its own folder lacks areferences/dir.python3 scripts/validate_repo.pyautomates the backtick and markdown-link forms of this check (check_backtick_paths,check_markdown_links); the manual pass here covers what the regex skips — bare filenames and paths embedded in prose. - Large files — working tree:
find . -type f -size +5M -not -path './.git/*'. History:git rev-list --objects --all | git cat-file --batch-check='%(objecttype) %(objectsize) %(rest)' | awk '/^blob/{print $2,$3}' | sort -rn | head. Flag big blobs and note whether they are in the working tree, history, or both. - Hooks cited vs present — for every
*.shnamed inCLAUDE.md,AGENTS.md,.claude/settings*.json, and.codex/hooks.json, confirm the file exists underhooks/. - Skill frontmatter — every
skills/*/SKILL.mdhas a YAML frontmatter block withnameanddescription. - Local artifacts ignored —
git status --shortshows no large untracked junk;git check-ignorecovers*.deb,**/node_modules/, and.ai/memory/projects/**/.browser-profile/. - Mirror parity —
python3 scripts/sync_skills.py --checkexits 0;skills/,.claude/skills/, and.agents/skills/are byte-identical (excludingworkspace/).
Guardrails
- Read-only. Never
Edit/Write/rm, nevergit push/filter-repo/rebase, never delete memory. - Cite a
pathor the exact command output for every finding. - Suggest a fix; do not apply it.
Output contract
| Severity | Area | Finding | Path / command | Suggested fix |
|----------|------|---------|----------------|---------------|Severity = Alta / Média / Baixa. End with a one-line verdict: clean, or N findings (M Alta).
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.

