Quality Gardening

Overview

Track quality as concrete metrics and debt movement, not as a vague single score.

This skill freezes new degradation first, then uses generated metrics to show current quality and convergence direction. For shared harness terms, see ../../references/harness-patterns.md; when quality surfaces are absent, use references/build-when-missing.md. For generated snapshot ownership, see references/generated-snapshot-ownership.md.

When To Use

• The user asks to design, evaluate, or maintain QUALITY_SCORE.md, quality reports, quality snapshots, debt reduction, or red lines.
• A repository needs structural metrics beyond lint and tests.
• The team needs periodic gardening instead of a one-time large refactor.

Inputs Needed

• Current quality pain points: large files, scattered events, direct API calls, duplicated entrypoints, missing tests, or similar risks.
• Source paths to scan and paths to exclude.
• CI or scheduled run strategy.