Quality Check

Overview

Purpose: Gate before declaring work complete. Catches obvious technical issues (type errors, linting, code review violations, test failures) before claiming a feature/task is done.

Key Principle: Fast feedback via sequential validation - stop at first failure to surface issues quickly.

When to Use This Skill

DO use quality-check:

• Before marking a complete feature/task as done
• Validates the entire body of work, not individual steps
• User can explicitly call for on-demand validation