quietmachineworks

drydock

Raise a project's dependencies one proven step at a time, each committed alone so a later regression bisects to one name. What cannot be raised is held and priced, never pushed through. Use when asked to update or upgrade dependencies, handle a security advisory, resolve a version conflict, or lift a project that has drifted behind its ecosystem.

ratchet-add

Build a check that enforces a code rule, as a ratchet that freezes existing violations and fails on a rise, or as a gate that tolerates none. Use when the user says they no longer want something in a codebase, that a rule is never respected, that a mistake keeps coming back, or asks to prevent a regression, freeze technical debt, ban a pattern, or enforce a convention. Takes the rule as an argument.

Code & Development Listed

ratchet-audit

Report which of a project's stated code rules are actually enforced, and which could be. Use when asked which conventions are enforced, whether a rule is respected, what the CLAUDE.md or AGENTS.md rules are worth, or to review the gap between what a project says and what it checks. Read-only, writes nothing.

refit

Execute one repair on a codebase with current behavior pinned before anything moves, and proof that nothing observable changed. Use when the user picks findings from a /qmw:survey report, asks to pay down a named piece of technical debt, to refactor something safely, or to clean up a pattern without breaking anything.

Code & Development Listed

seatrial

Run the release checklist for real before anything ships, from a clean clone to the built product smoked the way production runs it. Ends on go or no-go bound to one commit, fixes nothing. Use when asked whether something is ready to release, to verify a release, or before a tag, publish, or deploy.

shakedown

Play a real user through a product's UI, screen by screen, on a genuinely empty environment, until every screen in scope survives contact with reality. Use when asked to run a manual QA pass, a user-acceptance pass, "as a human, for real", to shake a product out before shipping, or to resume a pass already in progress.

Code & Development Listed

squawk

Run one reported bug from incident to proven fix, reproduced in a real browser before any code moves and proven through the UI afterwards. Use when a user reports a bug, a screenshot of a problem arrives, a production incident lands, or when asked to fix something and prove it rather than assume it.

survey

Audit an entire codebase, or one perimeter of it (front, back, mobile, infra), against the practices current for the stack it actually runs. Reports and prioritizes, fixes nothing, writes nothing. Use when asked for a code audit, a health check, a technical-debt review, or whether the code is over-engineered, duplicated or out of date.