audit-review
Use when completing tasks, implementing major features, or before merging — dispatches the-inspector to audit the books before the job is closed
- Installs
- 51
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/kucherenko/gangsta --skill audit-review- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads audit-review automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
The Audit: Requesting Code Review
Overview
Dispatch the-inspector to catch issues before they compound. The inspector gets precisely crafted context for evaluation — never the session's history. This keeps the inspector focused on the work product, not the thought process, and preserves your context for continued work.
Core principle: Audit early, audit often.
When to Request
Mandatory:
- After each task in parallel execution (The Hit)
- After completing a major feature
- Before merge to main
Optional but valuable:
- When stuck (fresh perspective)
- Before refactoring (baseline check)
- After fixing complex bug
How to Request
1. Get Git SHAs
BASE_SHA=$(git rev-parse HEAD~1) # or origin/main
HEAD_SHA=$(git rev-parse HEAD)
2. Dispatch the-inspector
Use the Task tool to dispatch the the-inspector agent with subagent_type: "the-inspector". Do NOT use "general" or "general-purpose" — these are not valid in a Gangsta Agents installation.
Fill the template at the-inspector-prompt.md in this skill directory with the following placeholders:
{WHAT_WAS_IMPLEMENTED}— What you just built{PLAN_OR_REQUIREMENTS}— What it should do (Contract clause, spec section){BASE_SHA}— Starting commit{HEAD_SHA}— Ending commit{DESCRIPTION}— Brief summary of the changes
3. Act on Findings
| Severity | Action |
|---|---|
| Critical | Fix immediately. Do not proceed until resolved. |
| Important | Fix before proceeding to the next task. |
| Minor | Note for later. Don't block progress. |
| Wrong | Push back with technical reasoning. |
Example
[Just completed implementing auth middleware]
1. Get SHAs:
BASE_SHA=$(git log --oneline | grep "previous task" | head -1 | awk '{print $1}')
HEAD_SHA=$(git rev-parse HEAD)
2. Dispatch the-inspector:
WHAT_WAS_IMPLEMENTED: JWT auth middleware with role-based access
PLAN_OR_REQUIREMENTS: Contract section 3.2 — Authentication
BASE_SHA: a7981ec
HEAD_SHA: 3df7661
DESCRIPTION: Added auth middleware, role guards, token validation
3. Inspector returns:
Strengths: Clean separation, real tests
Issues:
Important: Missing token expiry check
Minor: Magic number for token TTL
Assessment: Ready with fixes
4. Fix important issue, proceed to next task.
Integration with Heist Pipeline
- The Hit: Audit after each Crew Lead's territory completion
- Laundering: Final audit before the Don's approval
- Ad-hoc work: Audit before merge
Red Flags
Never:
- Skip audit because "it's simple"
- Ignore Critical issues
- Proceed with unfixed Important issues
- Argue with valid technical feedback without evidence
If inspector is wrong:
- Push back with technical reasoning
- Show code/tests that prove it works
- Use
gangsta:receiving-ordersfor processing feedback rigorously
Omerta Compliance
- Rule of Truth: Inspector reviews actual diffs, not claims
- Introduction Rule: Inspector communicates through the audit skill, not directly with Workers
FAQ
What does the audit-review skill do?
Use when completing tasks, implementing major features, or before merging — dispatches the-inspector to audit the books before the job is closed
How do I install audit-review?
Run npx skills add https://github.com/kucherenko/gangsta --skill audit-review in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/audit-review/ (personal) or .claude/skills/audit-review/ (project).
Which AI agents can use audit-review?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is audit-review safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains audit-review?
It is published by kucherenko in kucherenko/gangsta. It has 51 recorded installs.
More from kucherenko/gangsta
the-grilling
kucherenko/gangsta
Use when adversarial brainstorming is needed after reconnaissance — the Proposer, Devils-Advocate, and Synthesizer each run ONE pass (no rounds); the Don is grilled on the IDEA first, one question at a time, then the proposal is attacked
reconnaissance
kucherenko/gangsta
Use when beginning a new heist — deploys associates to survey the target codebase, existing tests, dependencies, documentation, and the ledger to produce a reconnaissance dossier for the don's review
using-gangsta
kucherenko/gangsta
Use when starting any conversation — establishes how to find and use Gangsta skills, enforces the 1% invocation rule, maps platform tools, and routes the Don's intent through the Gangsta Agents Family hierarchy
Popular security skills
azure-compliance
microsoft/azure-skills
Run Azure compliance and security audits with azqr plus Key Vault expiration checks. Covers best-practice assessment, resource review, policy/compliance validation, and security posture checks. WHEN: compliance scan, security audit, BEFORE running azqr (compliance cli tool), Azure best practices, Key Vault expiration check, expired certificates, expiring secrets, orphaned resources, compliance assessment.
minimal-run-and-audit
lllllllama/rigorpilot-skills
Rigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation command and write standardized reprooutputs/ files, including patch notes when repository files changed. Do not use for training execution, initial repo intake, generic environment setup, paper lookup, target selection, hidden scientific-meaning changes, or end-to-end orchestration by itself.
seo-audit
coreyhaines31/marketingskills
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," "indexing issues," "stuck on page 2," "striking distance keywords," "title tag rewrite," "low CTR," "local SEO," "Google Business Profile," or "map pack." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.
firebase-security-rules-auditor
firebase/agent-skills
Audits Firebase (Firestore, Cloud Storage) security rules for vulnerabilities, privilege escalation, role bypasses, create vs update inconsistencies, resource exhaustion, type safety, size limits, and hasOnly ownership checks. Use when auditing/reviewing rules, running red-team rule assessments, or scoring against auditor checklists. Don't use for Firebase CLI (login, deploy), Auth, Crashlytics, Remote Config, or database queries.
audit
pbakaus/impeccable
Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.
competitors
coreyhaines31/marketingskills
When the user wants to create competitor comparison or alternative pages for SEO and buyer-facing use. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' 'competitor teardown,' 'audit our competitor pages,' 'are our comparison pages out of date,' or 'competitive asset audit.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For auditing existing claims (not researching competitors from scratch, which is competitor-profiling; not technical SEO on these pages, which is seo-audit), use the asset audit here. For internal battle cards and sales-specific competitor docs, see sales-enablement.