audit
Skill157 starsChanged 33 days agoMITView on GitHub
Runs a multi-dimensional code quality, security, and integrity review with parallel subagents. User-invoked entry point via /audit; not for autonomous or subagent use.
- Deletes or force-pushes
193 other projects use a version of this.
Adopted by
Most recently taken up by
- danygiguere/audit-skillstheir own version, first seen Nov 16, 2026
- Deupaxx/EveryDay-Writertheir own version, first seen Nov 16, 2026
- vincentventalon/claude-code-video-editing-skilltheir own version, first seen Nov 15, 2026
- vincentventalon/my-claude-skillstheir own version, first seen Nov 15, 2026
- patrickjaja/claude-desktop-extratheir own version, first seen Nov 15, 2026
- authrain-cloud-abdullahformuli/unsloptheir own version, first seen Nov 15, 2026
Used with
Projects with it also use delight, teach-impeccable and 10 more.
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.
HK-hubSkilldelight
Add moments of joy, personality, and unexpected touches that make interfaces memorable and enjoyable to use. Elevates functional to delightful. Use when the user asks to add polish, personality, animations, micro-interactions, delight, or make an interface feel fun or memorable.
Also in 31 projects that use this
HK-hubSkillteach-impeccable
One-time setup that gathers design context for your project and saves it to your AI config file. Run once to establish persistent design guidelines.
Also in 18 projects that use this
zwy123zwySkillnormalize
将用户随意输入的提示词规范化为结构清晰、便于大模型执行的标准化提示词。适用于需要整理、统一提示词格式时调用。
Also in 18 projects that use this
ww-w-aiSkillpm-discovery
PM Agent Team - Automated product discovery, strategy, and PRD generation. Runs PM analysis workflow to produce comprehensive PRD before PDCA Plan phase.
Also in 3 projects that use this
ww-w-aiSkillqa-phase
Run QA tests at various levels (L1-L5) for features under PDCA management. Integrates with MCP tools to execute structured test plans.
Also in 3 projects that use this
- +7 more from HK-hub
Other versions193 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 193
- ccch1mneyyy/dsh-Go★ 24ksame name
- openai/plugins★ 7.8ksame name
- ccch1mneyyy/dsh-TUI★ 7.8ksame name
- macro-inc/macro★ 6.3ksame name
- yournextstore/yournextstore★ 5.5ksame name
- gadievron/raptor★ 4ksame name
- alchemy-run/alchemy-effect★ 2ksame name
- alchemy-run/alchemy★ 2ksame name
- mattmireles/gemma-tuner-multimodal★ 1.5ksame name
- jsmastery-pro/skills★ 1.4ksame name
183 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 repository68 other files it gives its agents.
- github-pages/agents.mdAGENTS.md
- adrSkill
- agent-protocolsSkill
- angular-idiomsSkill
- api-documentationSkill
- axum-idiomsSkill
- browser-automationSkill
- bugfixSkill
- chaos-testingSkill
- ci-cdSkill
- cli-developmentSkill
- code-reviewSkill
- cpp-idiomsSkill
- csharp-idiomsSkill
- data-engineeringSkill
- debugging-protocolSkill
- django-idiomsSkill
- dotnet-idiomsSkill
- elixir-idiomsSkill
- embedded-systemsSkill
- feature-flagsSkill
- flutter-idiomsSkill
- frontend-designSkill
- git-commit-integritySkill
- go-idiomsSkill
- guardrailsSkill
- hono-idiomsSkill
- incident-responseSkill
- java-idiomsSkill
- javascript-idiomsSkill
- kotlin-idiomsSkill
- laravel-idiomsSkill
- logging-implementationSkill
- ml-engineeringSkill
- mobile-designSkill
- mobile-testingSkill
- nextjs-idiomsSkill
- parallel-dispatchSkill
- payment-integrationSkill
- perf-optimizationSkill
- perf-optimizeSkill
- php-idiomsSkill
- postgres-idiomsSkill
- python-idiomsSkill
- rails-idiomsSkill
- react-idiomsSkill
- refactoring-patternsSkill
- refactorSkill
- research-methodologySkill
- ruby-idiomsSkill
- rust-idiomsSkill
- security-auditSkill
- sequential-thinkingSkill
- spring-boot-idiomsSkill
- sql-idiomsSkill
- structured-specSkill
- supply-chain-securitySkill
- swift-idiomsSkill
- testability-patternsSkill
- test-e2eSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
22 rules. 0 are common, 11 are distinctive, and 11 are very specific to this project.
0
Common
Most of the 173 edited versions we read keep these.
11
Distinctive
This author's own choices. Worth a look.
11
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
After another agent's feature is committed (cross-agent review)
- Distinctive: line 18
Before releases or deployments
- Distinctive: line 19
When user wants assurance without writing new code
- Distinctive: line 20
After addressing review findings, to verify the fixes
- Very specific: line 24
When writing new features → /workflow-solo or /workflow-team
- Very specific: line 25
When fixing known bugs → /bugfix
- Very specific: line 26
When restructuring code → /refactor
- Distinctive: line 32
Before starting the audit, you MUST:
- Distinctive: line 41
Before dispatching subagents, understand the codebase structure and scope.
- Very specific: line 84
Use invoke_subagent to spawn all activated dimension agents in a single call.
- Very specific: line 97
When all subagents message findings ready, proceed to Phase 2.
- Distinctive: line 105
Run the full validation suite for the project:
- Very specific: line 106
Linters and static analysis: Run language lint checks (npm run lint, golangci-lint run, cargo clippy, ruff check).
- Distinctive: line 109
Coverage report: Check test coverage if tooling is available.
- Very specific: line 111
Write results to .agentwork/findings-audit-verification.md:
- Very specific: line 126
Read all .agentwork/findings-audit-*.md files from Phase 1 and Phase 2.
- Distinctive: line 139
When findings from 2+ dimensions converge on the same module or function, escalate severity by one level (MINOR → MAJOR, MAJOR → CRITICAL):
- Very specific: line 156
Create the docs/audits/ directory if it doesn't exist
- Very specific: line 157
Read the report template from references/audit-report-template.md
- Very specific: line 159
Write the report to docs/audits/review-findings-{feature}-{YYYY-MM-DD}-{HHmm}.md
- Distinctive: line 167
After the audit produces findings, choose the right workflow based on finding type and severity:
- Distinctive: line 178
When starting a fix workflow in a new conversation, reference the persisted report:
“Common” is measured: kept by at least 6 in 10 of the 173 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
Audit Skill
Entry-point guard: This is a user-invoked command skill (
/audit). If you are a spawned subagent, do NOT execute this skill — return to your assigned scope card.
Purpose
Comprehensive, multi-dimensional code audit of existing code. Dispatches parallel subagents across orthogonal code quality, architectural, security, and integrity dimensions for maximum coverage. This skill identifies issues — it does not write new features or fixes.
When to Use
- After another agent's feature is committed (cross-agent review)
- Periodic quality gates on the codebase
- Before releases or deployments
- When user wants assurance without writing new code
- After addressing review findings, to verify the fixes
When NOT to Use
- Deep security-only vulnerability scan →
/security-audit - When writing new features →
/workflow-soloor/workflow-team - When fixing known bugs →
/bugfix - When restructuring code →
/refactor
References
references/audit-dimensions.md and references/audit-report-template.md — contains dimension scope cards, subagent prompt template, and report template.
Pre-Audit Checklist
Before starting the audit, you MUST:
- Scan
.agents/rules/directory — these form the baseline review criteria - Read
rule-priority.md— for conflict resolution and severity classification - Identify audit scope — determine whether auditing a specific feature, module, or full codebase
Phase 0: Reconnaissance
Before dispatching subagents, understand the codebase structure and scope.
0.1 — Stack & Architecture Detection
Scan for language/framework/infrastructure markers:
- Languages:
go.mod,package.json,Cargo.toml,pyproject.toml,pom.xml,*.csproj,Gemfile,composer.json - Frameworks: HTTP frameworks, ORMs, UI frameworks, state management
- Architecture: Directory layout, monorepo structure (
apps/), feature slice organization
0.2 — Codebase Inventory
Map key components within the audit scope:
- API endpoints and public entry points
- Business logic modules & pure domain functions
- Storage adapters & database interactions
- External service integrations & HTTP clients
- Logging, monitoring & observability setup
- Configuration and environment variable usage
- Test suite structure (unit, integration, E2E)
0.3 — Dimension Selection
Activate the applicable dimensions for the codebase under audit. State your selection explicitly:
| Dim | Scope | Activate When |
| A | Security & Configuration | Always |
| B | Reliability & Error Handling | Always |
| C | Testability & Architecture | Always |
| D | Observability & Operations Logging | Always |
| E | Code Quality & Patterns | Always |
| F | Integration Contracts & Database | Project has API boundaries or database |
| G | Dependencies & Test Coverage Gaps | Always |
State your selection:
"Activating dimensions: A, B, C, D, E, G. Skipping F (no API boundaries or database in this scope)."
Phase 1: Multi-Dimensional Audit Scan
Dispatch parallel subagents — one per activated dimension. Each operates independently with no cross-talk.
Dispatch Protocol
Use invoke_subagent to spawn all activated dimension agents in a single call.
Per-dimension fields:
- TypeName:
self(universal spawn mechanism — ensures subagents inherit full toolsets peragent-protocols§3) - Role:
Code Auditor — Dimension {KEY}(e.g.,Code Auditor — Dimension A) - Workspace:
inherit - Prompt: Build from the system prompt template in
references/audit-dimensions.md. Fill in: dimension name, scope card, and reconnaissance context from Phase 0.
Each subagent receives in its prompt:
- Dimension scope card — from
references/audit-dimensions.md - Reconnaissance context — stack + codebase inventory from Phase 0
- Output target —
.agentwork/findings-audit-{dimension-key}.md
When all subagents message findings ready, proceed to Phase 2.
Phase 2: Automated Verification
Run after all Phase 1 subagents report back. Run tools yourself as coordinator.
Run the full validation suite for the project:
- Linters and static analysis: Run language lint checks (
npm run lint,golangci-lint run,cargo clippy,ruff check). - Full test suite: Execute unit and integration tests (
npm test,go test ./...,cargo test,pytest). - Build check: Build the project binaries or bundles (
npm run build,go build,cargo build). - Coverage report: Check test coverage if tooling is available.
Write results to .agentwork/findings-audit-verification.md:
## Verification Suite Summary
- **Lint:** PASS / FAIL (details)
- **Tests:** PASS / FAIL (N passed, N failed)
- **Build:** PASS / FAIL (details)
- **Coverage:** N%Phase 3: Synthesis & Prioritization
3.1 — Collect
Read all .agentwork/findings-audit-*.md files from Phase 1 and Phase 2.
3.2 — Deduplicate
Consolidate findings reported by multiple dimensions (same root cause). Note which dimensions flagged each.
3.3 — Severity Ranking
Classify all findings using the standardized 4-level taxonomy:
- CRITICAL — vulnerabilities, data loss, app crashes; must fix immediately
- MAJOR — structural violations, missing I/O error handling, broken contracts; fix before release
- MINOR — code maintainability, function length violations, minor test gaps; fix near term
- ENHANCEMENT — non-critical improvements, defense-in-depth, documentation; backlog
3.4 — Cross-Dimension Correlation
When findings from 2+ dimensions converge on the same module or function, escalate severity by one level (MINOR → MAJOR, MAJOR → CRITICAL):
- Hardcoded secret (A) + secrets exposed in log output (D) → escalate to CRITICAL
- Missing error handling (B) + unlogged operation (D) on same endpoint → escalate to MAJOR
- Missing DB adapter test (G) + un-indexed foreign key (F) → escalate to MAJOR
Phase 4: Audit Findings Report
Output location: docs/audits/review-findings-{feature}-{YYYY-MM-DD}-{HHmm}.md
You MUST save the report to the repo (not just as a conversation artifact) so it can be:
- Referenced from other conversations/agents
- Tracked in version control
- Passed as context to fix workflows
Steps:
- Create the
docs/audits/directory if it doesn't exist - Read the report template from
references/audit-report-template.md - Fill all sections with Phase 3 findings
- Write the report to
docs/audits/review-findings-{feature}-{YYYY-MM-DD}-{HHmm}.md
Zero-Findings Guard: If the audit produces fewer than 3 findings, you MUST complete the "Dimensions Covered" attestation section in the report before declaring a clean result. This proves cross-boundary coverage was not skipped.
Feedback Loop
After the audit produces findings, choose the right workflow based on finding type and severity:
| Finding Type / Severity | Example | Workflow |
| CRITICAL | Hardcoded secret, SQL injection, data loss risk | /bugfix — immediate priority |
| MAJOR / Structural | Swallowed I/O errors, missing interfaces, pattern drift | /bugfix or /refactor |
| MINOR / Small fix | Missing operation log, function length > 50 lines | /bugfix or direct fix |
| ENHANCEMENT | Defense-in-depth, doc comment, type branding | /workflow-solo or backlog |
| Missing capability | New endpoint missing, missing auth check | /workflow-solo in a new conversation |
Using Findings in Other Contexts
When starting a fix workflow in a new conversation, reference the persisted report:
"Fix the critical and major issues in
docs/audits/review-findings-gatekeeper-2026-02-16-1430.md"
The agent in the new context can read the file directly from the repo — no need to copy-paste findings.
Completion Criteria
- Pre-Audit Checklist completed (rules scanned, priority understood, scope set)
- Reconnaissance completed (stack detected, codebase mapped, dimensions selected)
- All activated dimensions scanned by parallel subagents
- Automated verification suite executed (lint, tests, build, coverage)
- Findings synthesized, deduplicated, and severity-ranked
- Cross-dimension correlations identified and severity escalated
- Findings document saved to
docs/audits/in the repo - Remediation action plan documented
.agentwork/directory cleaned up (rm -rf .agentwork/)
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.

