← ClaudeAtlas

qualitylisted

Reviews code, pull requests, or a defect backlog for escaped-defect risk -- Pillar 2 of The Five Pillars. Use when reviewing a PR or batch of recently merged PRs, after a production defect to find the process gap, or when setting up quality gates for a new team or repo.
ClearMeasureLabs/cmstack · ★ 0 · Code & Development · score 60
Install: claude install-skill ClearMeasureLabs/cmstack
# /quality -- Establish Quality **Pillar 2 of The Five Pillars.** Reviews code, pull requests, or a defect backlog for escaped-defect risk. ## When to invoke - Reviewing a PR or a batch of recently merged PRs - After a production defect, to find the process gap that let it through - Setting up quality gates for a new team or repo ## What it checks 1. **Defect trend** -- are escaped defects (bugs found in production, not in review/QA) trending up, flat, or down over the last several releases? 2. **Process controls** -- what stands between a developer's keystroke and production: code review, automated tests, static analysis, staging validation? Where are the gaps? 3. **Time to resolve** -- for the last several escaped defects, how long from report to fix? The book's bar is minutes, not hours or days. ## Inputs Pull real data before reviewing -- don't guess at trend or process controls: - **PRs** -- `gh pr list --state merged --limit 5 --json number,title,url,reviews` (or the user pastes PR links/diffs directly) - **Escaped defects** -- the issue tracker's bug list filtered to "found in production" (`gh issue list --label bug`, Jira/Linear query, or a pasted defect log) - **Process controls** -- read the repo's CI config (`.github/workflows/`, `azure-pipelines.yml`, etc.) and branch protection settings rather than assuming what's enforced - If none of this is available, say so explicitly in the output instead of estimating numbers ## Example output > **Quality review -