quick

To make small code changes with verification, use an evidence-guided workflow that tracks edits, enforces inline planning, and logs safe git commits with scope awareness. This ensures lightweight fixes are executed safely without skipping validation.

Fixing typos and renaming constants requires a lightweight, contained multi-file update workflow. By assigning a task ID and enforcing strict edit-scope gates, the process tracks changes safely and escalates automatically if the scope grows beyond a few edits.

To control task scope and prevent unnecessary large edits, enforce a strict edit-limit path like a three-edit maximum. This practical edit-scope gate restricts lightweight execution to targeted fixes and automatically escalates when the required changes exceed the limit.

Yes, you can add research and discussion steps to a quick code editing workflow through composable rigor flags. Start with minimal execution, then append discussion, research, or full verification flags to increase evidence and safety as needed.

The --trivial flag works for contained multi-file updates but enforces a strict maximum of three edits. If your multi-file update requires more changes, the scope control mechanism automatically escalates the task to a higher tier for complex work.