Fix, Verify, and Lock Down

This skill covers the full lifecycle: from a pile of known issues to a codebase where every fix is proven and guarded by tests. The three phases build on each other -- skipping straight to tests without disciplined fixing and verification is how regressions slip through.

Phase 1: Catalog Every Issue

Before touching any code, build a complete inventory. This is the tracking backbone that prevents issues from falling through the cracks.

How to catalog

Review the conversation, error logs, code review comments, or whatever source identified the problems. For each issue, capture: