software qa bug finder

The problem

Green tests often provide a false sense of security. Code can pass the CI pipeline while containing race conditions, weak assertions, or implementation flaws that bypass the test logic entirely.

What it does

• Identifies tests that pass prematurely due to shallow assertions or incorrect async handling.
• Traces production code paths against specifications to find unhandled edge cases and swallowed errors.
• Audits localStorage, cookies, and mocks for state pollution that causes flaky test isolation.
• Verifies that test data and fixtures actually match the current implementation and requirements.
• Provides a structured PASS/FAIL/NEEDS REVIEW verdict with specific file and line number fixes.

Frameworks & tools

Cypress, Playwright, Jest, and Vitest.

Why this beats prompting it yourself

Standard prompts often take code at face value or assume green tests are correct. This skill uses a rigorous six-phase audit that treats the test suite as a suspect, looking for tautologies and timing bugs that generic analysis misses.

Use cases

• Auditing a new feature before merging to ensure the tests actually prove the requirements.
• Debugging intermittent CI failures caused by shared state or localStorage timing.
• Identifying "ghost tests" that assert UI existence but ignore functional state changes.

Known limitations

Requires access to task specifications and source files to be effective. It performs static inference and focused test execution rather than full environment setup.