repo-audit
Skill6 starsChanged 20 days agoApache-2.0View on GitHub
Audit existing frontend, Java, or Rust surfaces read-only. Use repo-review for change-based reviews.
24 other projects use a version of this.
Adopted by
Most recently taken up by
- albkhachikyan/claude-code-repo-audittheir own version, first seen Nov 15, 2026
- iuliandita/skillstheir own version, first seen Nov 15, 2026
- TheVeller/claude-skillstheir own version, first seen Nov 2, 2026
- ekajaya740/skillstheir own version, first seen Nov 1, 2026
- 0xUrsanomics/utopia-ostheir own version, first seen Nov 1, 2026
- DentalEdge-Solutions/claude_codetheir own version, first seen Nov 1, 2026
Used with
Projects with it also use handoff and code-review.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillhandoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 3 projects that use this
GoogleSkillcode-review
Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.
Also in 3 projects that use this
Other versions24 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 24
- zebbern/claude-code-guide★ 4.7ksame name
- Kanevry/session-orchestrator★ 53same name
- iuliandita/skills★ 12same name
- Megaprompting/torque-loop★ 10same name
- sunitghub/canon-skills★ 9same name
- my-chiefmind/ai-maestro★ 6same name
- nikkogibler/cabinet★ 4same name
- TheVeller/claude-skills★ 4same name
- conorbronsdon/repo-audit★ 3same name
- 0xUrsanomics/utopia-os★ 2same name
14 more not listed
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 repository23 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- skills/CLAUDE.mdCLAUDE.md
- api-specSkill
- ask-aiSkill
- dev-frontendSkill
- dev-javaSkill
- dev-rustSkill
- dev-testsSkill
- dev-typescriptSkill
- domain-modelingSkill
- human-writingSkill
- ops-browserSkill
- ops-clientSkill
- ops-deviceSkill
- product-specSkill
- repo-deliverySkill
- repo-mapSkill
- repo-reviewSkill
- to-taskSkill
- ui-specSkill
- work-retroSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 20 edited versions we read keep these.
1
Distinctive
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
- Very specific: line 35
Do not edit source, mutate Git, replace repo-review, or claim browser/client/runtime coverage without that evidence.
- Distinctive: line 45
Read rule priority for every audit route.
“Common” is measured: kept by at least 6 in 10 of the 20 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
Repository Audit
Entry Gate
Audit declared existing path scope only. Require a language/profile and evidence basis; do not turn broad exploration into a change-basis review, source fix, or runtime claim.
Route Map
| Request condition | Read | Result |
| Any audit route | rule priority | Resolved evidence authority |
| Frontend baseline | frontend profile and frontend checklist | Selected frontend concerns |
| Frontend architecture, state/data, or component ownership applies | architecture, state/data, and/or components | Concern-specific findings |
| Frontend styling, CSS, layout, or design-system concern applies | styling systems, style/layout, CSS, and/or layout governance | Concern-specific findings |
| Frontend framework, build, accessibility/performance, desktop, or anti-pattern concern applies | framework, build, accessibility/performance, desktop, and/or anti-patterns | Concern-specific findings |
| Frontend selected-source, visual, or DESIGN authority applies | visual evidence, DESIGN compliance, visual direction, and/or specification authorities | Qualified visual findings/gaps |
| Frontend protocol concern applies | frontend protocol contracts | Qualified contract findings |
| Java baseline or engineering concern applies | Java profile, Java checklist, and Java engineering | Selected Java concerns |
| Java protocol concern applies | Java protocol contracts | Qualified contract findings |
| Rust baseline, architecture, ownership, API, async, or memory concern applies | Rust profile, Rust checklist, baseline/lifecycle, architecture, ownership/resources, errors/API, async, and/or memory | Selected Rust concerns |
| Rust unsafe/security, web/desktop, SQLite, performance, testing, or anti-pattern concern applies | unsafe/security, web/desktop, SQLite, performance, testing, and/or anti-patterns | Concern-specific findings |
| Rust agent-runtime concern applies | agent runtime | Runtime-boundary findings/gaps |
| Cross-profile quality, OpenAPI, grounding, or design concern applies | codebase design, code quality, OpenAPI governance, and/or project grounding | Cross-boundary findings/gaps |
Invariants
- Audit only the declared profile/path scope; a miss or static signal is not absence/runtime proof.
- Findings need owner, reachability, concrete impact, and falsifiable validation.
- Do not edit source, mutate Git, replace
repo-review, or claim browser/client/runtime coverage without that evidence.
Output Map
Return profile, scope/basis, findings, evidence, checks, exclusions, and Not verified gaps.
Calibrate severity by demonstrated impact and urgency: P0 is catastrophic, active or readily reachable, and immediately blocking; P1 is high-impact risk that should block delivery; P2 is a meaningful scoped defect; P3 is a minor actionable improvement. State reachability or impact uncertainty instead of treating an unverified worst case as established.
Reference Map
- Read rule priority for every audit route.
- Load only the concern-specific references in the selected Route Map row; do not load an entire language group by default.
- Maintainers/calibration only: read eval cases, frontend scenarios, Java scenarios, Rust scenarios, frontend corpus, or Rust corpus; do not load them during ordinary runtime.
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.

