code-quality-principles

What problem does it solve?

This skill provides a concrete ruleset and operational checklist to prevent accidental, low-quality, or insecure changes during development and autonomous edits by ensuring every change is intentional and reviewable.

Core Features & Use Cases

• Iron Law: Require intentionality for every change and revert unexplained edits.
• Boy Scout Rule: Apply small, proximity-tested cleanups to files you already modify and record them as improve: commits when appropriate.
• Production Standards: Prevent secrets in commits, disallow TODOs and debug prints in shipped code, and avoid mocks/stubs or commented-out code in production.
• Quality Execution: Run lint, test, and type checks as parallel commands; classify first-touch files and enforce atomic commits and self-review checklists.
• Use Case: Use this skill to audit a proposed pull request, flag policy violations, and enumerate proximity-eligible cleanups before committing.

Quick Start

Use the code-quality-principles skill to audit a planned change and list any required cleanups, secrets, or policy violations before committing.