fix-issue

You can automate GitHub issue implementation by using a verifier-first, self-correcting loop in an isolated git worktree. This process tackles one issue at a time, ensuring all acceptance criteria are met before producing the final code.

The verifier-first issue implementation approach supports Rust, Scala 3, and ZIO 2 projects. It checks that all acceptance criteria are met before generating the final ship-ready code for these specific environments.

Yes, you need GitHub CLI, git, and cargo to execute the automated issue implementation. These dependencies are required to manage the repository, create isolated worktrees, and run the necessary build and verification commands.

Isolated worktree usage prevents main codebase contamination by creating a separate, clean work environment for the issue resolution process. This ensures that ongoing implementation and verifier-first checks do not affect the primary branch until the code is ship-ready.

The best way to track the automated code implementation process is through a durable run-log. This log records the entire verifier-first, self-correcting loop, providing a comprehensive history for auditing and debugging purposes.

No, you cannot implement multiple GitHub issues simultaneously. The self-correcting loop maintains a single-issue focus, tackling one GitHub issue at a time to ensure quality, prevent contamination, and verify all acceptance criteria are met.