repo-audit
Skill53 starsChanged 31 days agoMITView on GitHub
Use this skill when the user wants to audit a repository for baseline compliance, check code quality, security posture, CI/CD setup, testing, documentation, and ecosystem configuration. Runs 9 checklist categories and emits a Markdown report plus JSON sidecar at .orchestrator/metrics/repo-audit-<timestamp>.json. <example>Context: User is in a project repo and wants a baseline compliance check. user: \"/repo-audit\" assistant: \"Running repo-audit across 9 categories — Configuration, Code Quality, Git Hygiene, CI/CD, Testing, Security, Documentation, Clank Integration (optional), and MCP Configuration. Will produce a Markdown checklist report and JSON sidecar.\" <commentary>The user wants a compliance check; this skill is appropriate because it runs all 9 categories with pass/fail/warn/skipped statuses and writes structured output.</commentary></example>
Files
repo-audit
Portable mirror — generated, do not edit. The canonical workflow lives at
skills/repo-audit/SKILL.md; read that file for the full instructions. This mirror carries only agentskills.io-spec-legal frontmatter so harnesses that discover skills under.agents/skills/can find and route to the skill.Regenerate with
node scripts/generate-agents-skills.mjs.
Read the linked document in full and follow its complete workflow, including prechecks and stop conditions. Resolve its link relative to this SKILL.md, not the project working directory. The plugin root is three directories above this file. Resolve package paths such as skills/ and scripts/ from that root and relative links in the canonical document from its own directory. Keep the user’s project as the target of project operations.
$ARGUMENTS means the trailing user input after the selected command skill, or an empty string when absent. Preserve flags, quoted text, and Unicode as data. Do not perform global substitution in the command document, shell expansion on the argument string, or execution of that string as shell code. Pass command arguments through structured tool parameters or safely quoted individual arguments.
Other versions22 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 22
- zebbern/claude-code-guide★ 4.7ksame name
- iuliandita/skills★ 10same name
- Megaprompting/torque-loop★ 10same name
- sunitghub/canon-skills★ 9same name
- my-chiefmind/ai-maestro★ 6same name
- nikkogibler/cabinet★ 4same name
- conorbronsdon/repo-audit★ 3same name
- TheVeller/claude-skills★ 3same name
- 0xUrsanomics/utopia-os★ 2same name
- declancowen/skills★ 2same name
12 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.
Used alongsideProjects 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
In this repository167 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/000-session-orchestrator.mdcCursor rule
- .cursor/rules/010-session-workflow.mdcCursor rule
- .cursor/rules/020-quality-gates.mdcCursor rule
- .cursor/rules/030-wave-execution.mdcCursor rule
- .cursor/rules/040-discovery.mdcCursor rule
- .cursor/rules/050-plan.mdcCursor rule
- .cursor/rules/060-evolve.mdcCursor rule
- .cursor/rules/070-gitlab-ops.mdcCursor rule
- .cursor/rules/080-ecosystem-health.mdcCursor rule
- site/llms-full.txtllms.txt
- site/llms.txtllms.txt
- architectureSkill
- autopilotSkill
- bootstrapSkill
- brainstormSkill
- claude-md-drift-checkSkill
- closeSkill
- convergence-monitoringSkill
- debugSkill
- discoverySkill
- dispatcherSkill
- docs-orchestratorSkill
- ecosystem-healthSkill
- eli5Skill
- evalSkill
- evolveSkill
- frontmatter-guardSkill
- gitlab-opsSkill
- gitlab-portfolioSkill
- goSkill
- grillSkill
- harness-auditSkill
- hook-developmentSkill
- mcp-builderSkill
- memory-cleanupSkill
- mode-selectorSkill
- npm-publishSkill
- peekaboo-driverSkill
- persona-panelSkill
- planSkill
- playwright-driverSkill
- portfolioSkill
- quality-gatesSkill
- reconcileSkill
- releaseSkill
- remote-offloadSkill
- session-endSkill
- session-planSkill
- sessionSkill
- session-startSkill
- spinoutSkill
- sunset-reviewSkill
- templates-ackSkill
- test-auditSkill
- test-runnerSkill
- testSkill
- tmux-layoutSkill
- using-orchestratorSkill
- The first 60 shown.
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.