fix-issue

End-to-end GitHub issue resolution is automated using procedural gates that enforce step sequencing for implementation, validation, and closure across code, tests, and documentation. This prevents scope creep and ensures verification before closing tracked issues.

Procedural gates are gate-based checkpoints like ship-it, pre-mortem, zero-in, sanity-check, guard-scope, and verify-complete. They enforce discipline during issue resolution by requiring verification capture and metadata validation before advancing to the next workflow step.

To start an automated workflow to fix a tracked issue, invoke the fix-issue command with a Weave node ID or GitHub issue number. This initiates the end-to-end gated workflow, guiding the process from initial understanding through to final closure.

Yes, this gated issue resolution workflow supports both GitHub issues and Weave nodes. It applies procedural gates to tracked issues requiring implementation, validation, and closure, capturing done criteria and learning metadata when closing either type.

To prevent scope creep when fixing issues across code, tests, and documentation, use a gated workflow with a guard-scope checkpoint. This enforces strict scope boundaries and requires verification capture through gate commands and hooks before allowing issue closure.

The best way to ensure code review validation before closing an issue is to use procedural gates like verify-complete and sanity-check. These gate-based checkpoints enforce verification capture across code, tests, and documentation, reducing regressions before final closure.