guardsman

Calibrated, verified, convention-consistent engineering judgment for coding tasks. Reads the codebase's conventions and the change's real risk before writing code, verifies the check it leaves behind before letting anything pass, and tracks deliberate shortcuts in a logbook instead of a stray comment that rots. Five modes: build (default, persistent), review (diff), audit (repo-wide), logbook (harvest shortcuts), post-report (real per-repo status, no invented numbers). Use on ANY coding task: writing, adding, refactoring, fixing, reviewing, or auditing code, and choosing libraries or dependencies. Also use when the user says "guardsman", "stand the post", "challenge this diff", "right-size this", "logbook", "post report", "verify before you ship", "is this over-engineered", "what can we delete", or complains about bloat, boilerplate, unnecessary dependencies, or code that does not match the codebase. Do NOT use for non-coding requests (general knowledge, prose, translation, summaries, recipes).