brutal-exhaustive-audit

Audit build, routes, data flow, user journeys, and edge cases across five passes.

Updated Aug 20, 2025
One-click install
npx skills add https://github.com/BRANDNEWSHVT/mercora --skill brutal-exhaustive-audit-brandnewshvt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brutal-exhaustive-audit
Source: https://github.com/BRANDNEWSHVT/mercora/tree/main/storefront-nuxt/.agents/skills/brutal-exhaustive-audit
Command: npx skills add https://github.com/BRANDNEWSHVT/mercora --skill brutal-exhaustive-audit-brandnewshvt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Thoroughly verifies every file, route, data flow, and user path to prevent gaps and ensure nothing is missed during product audits.

Core Features & Use Cases

  • Enforces five mandatory passes (Build & Static Analysis, Route & Page Verification, Data Flow Tracing, User Flow Testing, Edge Case Validation) with explicit checklists.
  • Produces actionable task lists with clear root causes, evidence, and acceptance criteria for remediation.
  • Ideal for release readiness, large refactors, API integrations, and complex cross-cut validation.

Quick Start

Run the five-pass brutal audit on the current project to generate a complete task list.

Frequently Asked Questions about brutal-exhaustive-audit

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

FAQPage Schema
What is an end-to-end product audit and when do I need one?

An end-to-end product audit verifies every file, route, data flow, and user path to prevent gaps. You need this exhaustive audit during release readiness, large refactors, API integrations, and complex cross-cut validation to ensure nothing is missed.

How do I perform an exhaustive audit of my application routes and data flow?

To perform an exhaustive audit, apply five mandatory passes across all routes, components, and data sources. These passes cover build and static analysis, route verification, data flow tracing, user flow testing, and edge case validation to document every issue.

What's the best way to document edge cases and user journey issues for remediation?

The best way to document edge cases is generating actionable task lists with clear root causes, evidence, and acceptance criteria. This ensures remediation teams receive explicit documentation of every identified issue across all user journeys.

Does this exhaustive audit approach work for large refactors and API integrations?

Yes, this exhaustive audit approach is ideal for large refactors and API integrations. It enforces comprehensive coverage by applying mandatory passes to all data sources and components, ensuring complex cross-cut validation identifies every issue.

How do I ensure comprehensive QA coverage across all components and data sources?

Ensure comprehensive QA coverage by applying the five mandatory passes to all routes, components, and data sources. This brutal audit method verifies build integrity, traces data flow, and validates edge cases to prevent missed problems.

Why does my release readiness review keep missing edge cases and data flow problems?

Your release readiness review misses edge cases because it lacks exhaustive end-to-end verification. Applying five mandatory passes across data flow tracing and edge case validation ensures complete coverage and produces actionable tasks with evidence.