bug-audit
by abczsl520
Coding Agents & IDEsBrief
Dynamic bug hunting for Node.js projects — profiles each project, then selects from 9 audit modules. 200+ real-world pitfalls.
Description
What This Skill Does
A structured 6-phase audit methodology for Node.js web projects. It reads the codebase to build 7 project-specific tables covering API endpoints, state machines, timers, numeric values, data flows, resource ledgers, and concurrency hotspots, then verifies each row exhaustively. Supports games, data tools, WeChat apps, API services, bots, and dashboards.
Builds project-specific audit tables from actual code rather than running a generic checklist, so it catches logic bugs and data flow vulnerabilities that automated scanners miss.
When to Use It
- Auditing a game backend for exploitable economy or scoring bugs
- Finding race conditions in payment or coupon redemption flows
- Checking a WeChat mini-app for OAuth and session vulnerabilities
- Reviewing an API service for auth bypass and rate abuse
- Verifying state variables reset correctly between game rounds
Example Workflow
User asks: audit my Node.js game backend for bugs and vulnerabilities
- 1
Read all project files and identify the project type
- 2
Build 7 audit tables: API endpoints, state machines, timers, numeric values, data flows, resource ledgers, and concurrency hotspots
- 3
Verify each table row, rating each finding as critical, medium, minor, or OK
- 4
Run red team attack chains (universal + game-specific) and verify blue team defenses for each critical finding
- 5
Run supplementary generic checks from modules.md matching the project type
Numbered bug list with severity ratings, root causes, fix recommendations, and affected files, plus an archive entry documenting tables built and key pitfalls
Installation
clawhub install abczsl520/bug-auditRun the CLI command, or paste the prompt into Claude Code, Cursor, Codex or whichever coding agent you use.