skills.rest
snqb
snqbCOMMUNITY
Explore all skills by this author →
GitHub

latent-bug-audit

Audit codebases for latent bug patterns and report structured findings.

1|Updated Feb 17, 2026
Search Tags:#testing#debugging#audit#async#code-quality#static-analysis#latent-bug
One-click install
npx skills add https://github.com/snqb/my-skills --skill latent-bug-audit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: latent-bug-audit
Source: https://github.com/snqb/my-skills/tree/main/latent-bug-audit
Command: npx skills add https://github.com/snqb/my-skills --skill latent-bug-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Find bugs that typically slip through tests by auditing common latent-bug classes across code paths, concurrency, I/O, and data lifecycles.

Core Features & Use Cases

  • Automated detection of 12 latent bug classes including network I/O, silent data loss, session leaks, blocking I/O in async contexts, and more.
  • Structured reporting with file:line, bug class, impact severity, and concrete fixes to guide remediation.
  • Use cases include pre-deployment audits, post-incident reviews, and periodic health checks of large codebases.

Quick Start

Run a latent-bug-audit on the target repository to surface actionable findings.

Frequently Asked Questions about latent-bug-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a latent bug audit and how does it find intermittent failures?▼

Static analysis for latent bugs detects 12 common bug classes, including network I/O in hot paths, blocking I/O in async contexts, and session leaks. It audits code patterns across modules and DB interactions to find issues that typically slip through standard tests.

How do I find race conditions and silent data loss in async tasks?▼

You can detect silent data loss and session leaks by auditing code paths and data lifecycles. The audit applies best-practice checks to modules with DB interactions, returning structured findings that detail the bug class, impact severity, and specific remediation steps.

Can I use static analysis to find blocking I/O in async codebases?▼

Static analysis applies audit rules to codebases with multiple modules and asynchronous tasks to identify blocking I/O and race conditions. It returns structured findings with file:line locations, bug classes, impact severity, and concrete fixes for remediation.

What is the best way to audit code quality for pre-deployment health checks?▼

For periodic health checks and post-incident reviews, static analysis audits code patterns to detect latent bugs like session leaks and race conditions. It provides structured reporting that includes the bug class, impact severity, and guided remediation steps.

Does latent bug detection work on codebases with multiple modules and DB interactions?▼

Static analysis audits are designed for codebases with multiple modules and DB interactions, identifying 12 latent bug classes including race conditions and session leaks. It returns structured findings with file:line references, impact severity, and fixes.

Related Skills

Explore More Software Engineering Skills→
testdriveraitestdriverai
238

testdriver:focus-application

Focus a named application window via the TestDriver API for UI interactions.

Official
Intermediate
TienchingTienching
3

code-review

Review codebase diffs for security, quality, and maintainability issues.

Community
Advanced
Rune-kitRune-kit
82

review

Review code diffs for bugs, security issues, and project conventions.

Official
Advanced
baphledbaphled
1

static-analysis

Guide static code analysis tools to detect bugs, vulnerabilities, and style violations.

Community
Intermediate