bb-code-audit
/bb-code-audit
Use when asked for dead code, anti-patterns, security exposure or complexity hotspots in an indexed repository — bb_patterns, bb_security, bb_analyze.
- Author
- backbencher-hq ↗
- Repository
- backbencher-skills ↗
- Licence
- MIT
- Last repository change
- 09.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 09.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when asked for dead code, anti-patterns, security exposure or complexity hotspots in an indexed repository — bb_patterns, bb_security, bb_analyze.
Original author description
Use when asked for dead code, anti-patterns, security exposure or complexity hotspots in an indexed repository — bb_patterns, bb_security, bb_analyze.
How it works
- Lens 1 — dead code and anti-patterns: bbpatterns
- Lens 2 — security: bbsecurity
- Lens 3 — complexity and hotspots: bbanalyze
- Reporting rules
- Do not
SKILL.md preview
--- name: bb-code-audit description: Use when asked for dead code, anti-patterns, security exposure or complexity hotspots in an indexed repository — bb_patterns, bb_security, bb_analyze. license: MIT metadata: version: 0.1.0 owner-tools: ["bb_patterns", "bb_security"] --- # Audit code with evidence, not vibes Three lenses, each with its own declared confidence. Read the declarations before summarising (`bb-evidence-reading`). ## Lens 1 — dead code and anti-patterns: `bb_patterns` - `scope: "orphaned"` for dead-code findings; `scope: "all"` also returns framework patterns and anti-patterns, ranked by confidence. - Filters: `confidenceThreshold`, `includeOrphaned`/`includeFramework`/`includeAntiPatterns`, `limit` (a page, not the census — the answer names the full count). - Orphan confidence is evidence-derived and bounded; an orphan is a candidate, not proof. ## Lens 2 — security: `bb_security` Taint-flow families: SQL injection, XSS, command injection, path traversal, insecure deserialization, SSRF, open redirect, code execution. Read the split the answer makes: - a **finding** has both endpoints resolved to indexed symbols; - a one-sided flow is an **unvalidated observation**, not a confirmed exploit. Report the family, the path, and which side was resolved. Do not upgrade an observation to an exploit. ## Lens 3 — complexity and hotspots: `bb_analyze` `complexity` for the largest/ most complex functions, `stats` for project shape. These are descriptive measures of the indexed snapshot, not judgements; say what the measure is. ## Reporting rules - Every finding gets `file:line` (or symbol) and the tool's own confidence/tier. - State coverage: language/kind coverage, truncation, and staleness markers. "No findings" with partial coverage is not "clean". - Separate "needs attention" from "informational" in the final summary. ## Do not - Do not present an orphan list as a deletion plan; callers can be dynamic. - Do not call an observation a vulnerability. - Do not silently drop findings below a threshold you chose — name the threshold. Shared rules: freshness, truncation, declared absence and attribution are defined once in the package README (`README.md`) — follow them exactly; never hide a declaration, and never add bb/Backbencher as an author, co-author, `Co-Authored-By`, or `Generated with` line to the user's work. Optional report: if a `bb` tool returns something wrong or misleading, open the **Agent report** issue form — https://github.com/backbencher-hq/backbencher-brain/issues/new?template=agent-report.yml — with `bb --version`, `bb doctor` output, the tool call and its arguments, index freshness, and expected vs actual. Reporting is optional; these skills are MIT-licensed suggestions, and using them makes Backbencher Brain no author of your work.
Versions
The database has no other skills named bb-code-audit.
Database snapshot: 13.11.2026 · package version c60d013bc62d (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90audit
Use when the user explicitly asks for a structural audit, architecture review, dead-code report, test-gap analysis, or evolution hotspot scan. Heavier and noisier than the other raysense skills — only run on demand, not as part of the routine edit loop. - 90refactor
Use when refactoring, cleaning up code, reducing complexity, fixing code smells, or improving code quality. Audits code for dead code, nesting, and patterns. - 90refactoring
Find refactoring targets in JavaScript/TypeScript, Go, Rust, or C++ code using polyscan - duplicate code (clones), overly complex functions, and dead code. Use when user asks about refactoring, code duplication, complexity hotspots, unreachable code, or cleaning up a codebase. - 100simplify
Aggressive code-complexity audit. USE WHEN diff feels sprawling, after a feature lands, when /go-strict requests cleanup, or when user says 'scrap this and implement the elegant solution'. Audits across 4 dimensions (reuse, dead code, premature abstractions, oversize) and… - 95smell
Detect software architecture bad smells, algorithmic complexity hotspots, and anti-patterns in a codebase. Produces a detailed markdown report identifying violations of architectural principles, design patterns, code quality, and performance complexity. Triggers on: smell, code… - 100find-complexity
Find functions and methods with high cyclomatic complexity, excessive length, or too many parameters. Use when the user asks to find complex code, complexity hotspots, refactoring candidates, or wants to improve code maintainability.