fusion-fugu-coding

Controlled Fugu-lite coding workflow for bug fixes and feature work — plan (Thinker) then implement (Worker) then verify (Verifier) then Fusion review, with a bounded repair loop. Makes minimal edits; never commits, pushes, or touches secret files. Use to actually carry out a change end to end with guardrails.

Fugu-lite Thinker planning for a coding task before any edits. Classifies the task, inspects only relevant files, and produces an execution plan (objective, files, constraints, steps, test strategy, risks, rollback, verification commands, and a ready-to-use worker prompt). Does NOT edit files. Use before starting a non-trivial change.

Fugu-lite Verifier for the current changes — inspects git status/diff, detects the package manager and scripts, runs typecheck/lint/test/build where available, scans for secrets, runs a Fusion-lite review, and produces an approve / request_changes / needs_human_review decision. Does NOT implement new changes unless the user explicitly asks. Use to check work before committing.

Fusion-lite multi-agent code review of the current git diff or a provided patch/file. Spawns bug, test, security, and architecture reviewers, then a judge merges findings into one structured decision. Use for PR review, pre-merge checks, final verification, and bug/security/test sweeps.