Skip to content

abczsl520/bug-audit-skill

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

7 Commits
 
 
 
 
 
 

Repository files navigation

🔍 Bug Audit Skill

ClawHub License: MIT OpenClaw Skill

Don't run a checklist. Dissect the project, then exhaustively verify every entity.

Built from a hard lesson: a project took 21 rounds to find 172 bugs using generic checklists. Post-mortem revealed that building project-specific check matrices first would have caught most bugs in 3-4 rounds.

The Problem with Checklists

Generic checklists catch "known pattern" bugs (CORS, XSS, timezone). But most critical bugs are project-specific logic vulnerabilities:

  • buy API accepts cost=0 → free purchases (not in any checklist)
  • raid-result callable without calling buy first → infinite money exploit
  • Search completion doesn't verify distance → remote looting

These bugs live in the relationships between APIs, not in individual code patterns.

The Solution: Dissect → Verify → Supplement

Phase 1: Dissect — Read code, build 6 project-specific tables (10-15 min)
Phase 2: Verify  — Exhaustively check every row in every table
Phase 3: Supplement — Run generic modules as safety net
Phase 4: Regress — Check fixes didn't introduce new bugs
Phase 5: Archive — Record pitfalls for next audit

The 6 Tables

Table Extracts Key Question
API Endpoints Every route: method, path, auth, params Can I bypass? What if I send garbage?
State Machines Every state variable: setter, reader, lifecycle Does it leak across lifecycles?
Timers Every setTimeout/setInterval Does it fire after cleanup?
Numeric Values Every user-influenceable number What if 0? Negative? Huge?
Data Flows Every related API pair (buy→use) Can I skip Step 1 and call Step 2 directly?
Resource Ledger Every resource: all inflows, all outflows Is there an infinite loop?

Data Flows table is the most critical. The biggest bugs (buy bypass, missing raid tokens) hide in the links between APIs.

Install

clawhub install bug-audit

Or manually:

git clone https://github.com/abczsl520/bug-audit-skill.git ~/.openclaw/skills/bug-audit

Then say: "对这个项目执行bug排查" or "audit this project for bugs"

What's Inside

File Content
SKILL.md Core methodology: 6 tables + 5 phases
references/modules.md 9 generic audit modules for Phase 3
references/pitfalls.md 200+ real-world pitfalls + debugging techniques

Documentation

Full docs on the Wiki:

🔗 Part of the AI Dev Quality Suite

Skill Purpose Install
bug-audit (this) Dynamic bug hunting, 200+ pitfall patterns clawhub install bug-audit
codex-review Three-tier code review: quick scan → deep audit → adversarial clawhub install codex-review
debug-methodology Root-cause debugging, prevents patch-chaining clawhub install debug-methodology
nodejs-project-arch AI-friendly architecture, 70-93% token savings clawhub install nodejs-project-arch
game-quality-gates 12 universal game dev quality checks clawhub install game-quality-gates

License

MIT

About

OpenClaw skill: Dynamic bug audit for Node.js web projects (games, data tools, WeChat, APIs, bots). 200+ real-world pitfalls.

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors