CheckPickerUpper

@checkpickerupper source repo

6 skills
0 followers
11 hours ago last updated

▌
Pizza1 · checkpickerupper
Justify by correctness, never by convention. Use when a design, fix, API, macro, library surface, hook message, or naming decision is defended by 'it's what the codebase does', 'the established pattern', 'the canonical lane does it', 'more ergonomic', 'less churn', 'already wired', 'smallest fix', 'compatibility', 'legacy path', or 'out of scope to change'. Prevalence and transition size are not evidence. Re-derive from correctness, name the bug the alternative causes, and be confident in the correct call even when the codebase already happens to do it.

0
installs
▌
Readonly · checkpickerupper
User-invoked modifier for evidence-first read-only investigation. Use when the user appends /readonly to a question or another skill request: answer by checking the codebase and available read-only sources, do not implement, do not open issues, do not mutate local or remote state, and do not guess with 'likely' or 'probably' when evidence can be gathered.

0
installs
▌
Dependency Trace · checkpickerupper
Dependency trace: derive the correctness graph before implementation. Use when the user asks for dependency order, foundations, or a lowest-to-highest flow for a feature, especially when they ask for the correct road before implementation or reject MVP/fastest-path planning.

0
installs
▌
To Issues Clearly · checkpickerupper
Create GitHub issues from a plan, bug, finding, audit or PRD, whose titles a stranger can act on. Use when filing issues or turning work into issue-sized slices. Builds every title as what somebody wrote or did followed by what the system did with it, refuses words that exist only inside the codebase, and reads each title cold before publishing. Splits issues by whether anything visibly breaks; cuts vertically and sizes each to one fresh context window; sequences a wide refactor as expand-migrate-contract; puts the breakdown to the user before publishing anything; and wires real GitHub sub-issue edges rather than prose references.

0
installs
▌
Grill With Docs Requiem · checkpickerupper
A high-judgment design interview that sharpens plans in useful batches and records settled domain language and ADRs as the conversation progresses.

0
installs
▌
Antimatter Code Quality Review · checkpickerupper bundle
Total annihilation: no finding survives unless it survives refutation. An unusually strict maintainability and structural-quality audit of a diff — review frame, intent/spec fit, repo standards, abstraction quality, cohesion, type/boundary cleanliness, duplication, control-flow tangles, missed extractions and invented variation, data structures whose cost grows faster than they need to, allocation on repeating paths, and correct-by-construction opportunities. Use for a deep code-quality audit, a harsh pre-merge review, or to determine what structural change makes a class of bug impossible rather than merely caught. Stricter than a conventional review because every finding must survive an adversarial refutation pass, ship with a concrete before→after, and prove it preserves behavior. Severity theater is prohibited: only provable findings are reported.

0
installs

6 published skills