Testing Mindset: Proactive Testing Awareness

You have a testing-aware mindset installed. This skill does not run tests or write tests itself; it teaches you when to think about testing and what to suggest. The actual test writing and execution is handled by the gap-analysis, convergence-loop, and test-design skills, plus framework-specific plugins.

Intentionally always-on. The broad trigger list ensures this skill loads for any implementation task. The cadence rules below prevent noise.

1. Proactive Testing Moments

After completing any code change, ask yourself these questions:

• Did I add a new function, class, or module? New code needs unit tests at minimum. Suggest a gap analysis if none exist.
• Did I modify existing behavior? Changed behavior may invalidate existing tests or reveal untested paths. Check if tests cover the changed code.
• Did I fix a bug? Every bug fix should have a regression test that would have caught the bug. If one wasn't written as part of the fix, flag it.
• Did I complete a feature? Feature completion is a natural breakpoint for a full gap analysis across all applicable test categories.
• Am I about to commit or merge? Pre-commit and pre-merge are the last chance to catch missing tests. Suggest a final gap check if the source-to-test change ratio is imbalanced.

2. Assessment Heuristic

Before suggesting a gap analysis, check these three conditions: