← ClaudeAtlas

trellis-checklisted

Comprehensive quality verification: spec compliance, lint, type-check, tests, cross-layer data flow, code reuse, and consistency checks. Use when code is written and needs quality verification, before committing changes, or to catch context drift during long sessions.
vibex-ai/vibex · ★ 4 · Code & Development · score 74
Install: claude install-skill vibex-ai/vibex
# Code Quality Check Comprehensive quality verification for recently written code. Combines spec compliance, cross-layer safety, and pre-commit checks. --- ## Step 1: Identify What Changed ```bash git diff --name-only HEAD git status ``` ## Step 2: Read Task Artifacts and Applicable Specs Read the current task artifacts in order: - `prd.md` - `design.md` if present - `implement.md` if present ```bash python3 ./.trellis/scripts/get_context.py --mode packages ``` For each changed package/layer, read the spec index and follow its **Quality Check** section: ```bash cat .trellis/spec/<package>/<layer>/index.md ``` Read the specific guideline files referenced — the index is a pointer, not the goal. ## Step 3: Run Project Checks Run the project's lint, type-check, and test commands. Fix any failures before proceeding. ## Step 4: Review Against Checklist ### Code Quality - [ ] Linter passes? - [ ] Type checker passes (if applicable)? - [ ] Tests pass? - [ ] No debug logging left in? - [ ] No suppressed warnings or type-safety bypasses? ### Test Coverage - [ ] New function → unit test added? - [ ] Bug fix → regression test added? - [ ] Changed behavior → existing tests updated? ### Spec Sync - [ ] Does `.trellis/spec/` need updates? (new patterns, conventions, lessons learned) > "If I fixed a bug or discovered something non-obvious, should I document it so future me won't hit the same issue?" → If YES, update the relevant spec doc. ## Step 5: Cross-Layer Dimensio