tugtool

Analyze recent work, stage relevant files, and create a git commit with a clear, informative commit message.

Answer a question about the project's git history — commits, file history, and prior work — by searching real git context first, then citing shas.

Audit the implementation work for a plan (or a step range) AFTER it's built — assess code quality, coherence, technical choices, and architecture; audit it against the tuglaws and the real diff; then rule "fixups needed" or "codebase is in good shape"

Quick, plan-less, worktree-isolated work — agentless, in-thread, committing per round, stopping for review before merge

Implement a plan into a tested build on an isolated worktree — walk a single step, a step range, or the whole plan; agentless, in-thread, committing per step, stopping for review before merge

Devise an implementation plan in-thread — clarify the idea, write it against the devise skeleton, validate it — ready for /tugplug:implement

Vet a plan (or a step range within it) BEFORE implementation — assess plan quality, coherence, technical choices, and strategy; check it against the tuglaws and the real code; then rule "fixups needed" or "clear to implement"