properizelisted

# Properize Turn "I hacked this together for myself, it's AI slop, but I want it proper now" into a repo that meets lgtm-hq standards. This skill **sequences** other skills into one pipeline — it composes `commit`, design grilling, `issue`, and `implement-issues`/`pr`, it does not replace them. Never skip a stage or collapse two stages into one session; each stage produces an artifact (commits, a design decision, an issue tree) the next stage depends on. ## The mistake this skill prevents The default failure mode is jumping straight from "make this proper" to writing a full implementation plan and executing it in one pass — no commit checkpoint, no design interrogation, no issue trail. That produces an unreviewable mega-diff and bakes in whatever the prototype already got wrong. Do NOT do this. Do: commit → grill → recon → spec → implement, one stage at a time, stopping between stages for the artifacts to exist and be reviewable. ## Pipeline ### 1. Commit the WIP first Before any design discussion, get the current state to a lint-clean, committed baseline: - Drive `uv run lintro chk` to 0 issues. Fix real bugs the gate surfaces (missing imports, undefined names, missing arguments, type errors, dead-code/unused-variable warnings) rather than suppressing them — a lint gate on a prototype routinely finds actual bugs, not just style nits. - Land signed, semantic commits **grouped by domain**, not one giant commit. For example: a `cleanup` pass, then commits per fea