resonance-ops-audit

Orchestrates multi-specialist audits of branches and codebases into severity-ranked findings reports.

Updated Dec 1, 2025
One-click install
npx skills add https://github.com/manusco/wolfgang --skill resonance-ops-audit-manusco
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: resonance-ops-audit
Source: https://github.com/manusco/wolfgang/tree/main/.agents/skills/ops/audit
Command: npx skills add https://github.com/manusco/wolfgang --skill resonance-ops-audit-manusco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before merging a PR or cutting a release, a single reviewer often misses cross-domain risks like authorization bypasses, duplicated business logic, or untested failure paths. This Skill coordinates a swarm of specialist reviewers and consolidates their findings into one classified, decision-ready audit report. ## Core Features & Use Cases - Specialist Swarm Dispatch: Delegates security, code quality, QA, architecture, backend, and performance checks to dedicated specialist skills and aggregates their findings. - Severity-Normalized Reporting: Classifies every finding from P0 (blocker) to P3 (low) using the Audit Classification Taxonomy and ends with an explicit APPROVE or REJECT decision. - Authorization and Data Truth Audits: Verifies permission separation across the authorization model and detects duplicated business rules and environment-sensitive assumptions. - Use Case: Before merging an auth-related PR, run the audit to have security, reviewer, QA, and architect specialists examine the diff, then receive a single report ranking an IDOR vulnerability as P0 and rejecting the merge despite passing tests. ## Quick Start Ask the agent to run /audit on your current branch or a specific PR before merging it.

Frequently Asked Questions about resonance-ops-audit

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

FAQPage Schema
How do I audit a pull request before merging?▼

Run /audit on the branch or diff. The skill dispatches security, reviewer, QA, and architect specialists, then compiles their findings into a severity-ranked report with an explicit APPROVE or REJECT decision.

What does the audit severity ranking P0 to P3 mean?▼

P0 is a blocker such as an auth bypass or data leak, P1 covers auth ambiguity and duplicated business truth, P2 flags complexity hotspots and brittle tests, and P3 covers style and naming drift.

Can the audit reject a PR even when all tests pass?▼

Yes. Passing tests do not override structural findings. If the swarm uncovers P0 or P1 issues like missing authorization checks or untested crash paths, the audit explicitly states REJECT regardless of green test results.

When should I use a single specialist instead of the full audit?▼

Use a specialist directly, such as the security or QA skill, when you have a single-domain question. The audit conductor is intended for multi-domain verification of a repository, change set, or release surface.

Does the audit fix the issues it finds?▼

No. Fixing code is explicitly out of scope. The audit reports and classifies findings, then delegates remediation back to implementation or refactoring skills after the audit completes.