flywheel-audit

Audits a codebase for bugs, security issues, test gaps, and dead code using parallel agents.

3|1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/burningportra/agent-flywheel-plugin --skill flywheel-audit-burningportra
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flywheel-audit
Source: https://github.com/burningportra/agent-flywheel-plugin/tree/main/skills/flywheel-audit
Command: npx skills add https://github.com/burningportra/agent-flywheel-plugin --skill flywheel-audit-burningportra

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manual codebase audits are slow and inconsistent, and a single reviewer often misses entire categories of issues. This Skill coordinates multiple parallel audit agents so bugs, security vulnerabilities, test gaps, and dead code are all examined at once with consolidated findings. ## Core Features & Use Cases - Parallel Multi-Agent Audit: Spawns four background agents (bugs, security, tests, dead code) in full mode, or two agents in quick mode, coordinated through Agent Mail and a shared team. - Structured Findings Report: Synthesizes agent reports into a summary of critical bugs, security severities, missing tests, and removable dead code with file:line references. - Actionable Follow-Up: Offers to convert findings into tracked tasks and beads via TaskCreate and br create. - Use Case: Before a major release, run a full audit to have four agents simultaneously scan for race conditions, injection vulnerabilities, untested critical paths, and unused exports, then receive one consolidated report. ## Quick Start Ask the assistant to run a full codebase audit for bugs, security issues, test gaps, and dead code.

Frequently Asked Questions about flywheel-audit

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

FAQPage Schema
How do I audit a codebase for bugs and security issues with AI agents?

Run the audit in full mode, which spawns four parallel background agents covering bugs, security, test coverage, and dead code. Each agent reports findings with file:line references, and the coordinator synthesizes them into a single categorized summary.

What is the difference between full and quick audit mode?

Full mode spawns four parallel agents covering bugs, security, tests, and dead code. Quick mode uses only two agents for a faster, narrower pass. Full is the default when no mode is specified.

How do parallel audit agents coordinate without conflicts?

Agents bootstrap an Agent Mail session with macro_start_session and join a shared team created with TeamCreate. They report results to the coordinator via send_message, and the coordinator shuts each agent down individually after collecting findings.

What happens if an audit agent stops responding?

The coordinator saves each agent's task ID and can force-stop unresponsive agents with TaskStop. Idle agents that have not reported can be nudged with a direct SendMessage asking them to send their findings.

Can audit findings be turned into tracked work items?

Yes. After the audit, the coordinator asks whether to create beads for the findings. If confirmed, it uses TaskCreate to track each category and creates beads via br create with appropriate descriptions.