issue-runner

You can automate the full GitHub issue lifecycle by running each issue through a fresh orchestrator session that drives branch creation, planning, implementation, testing, review, and merge sequentially without manual coordination.

End-to-end issue workflow automation includes branching, planning, implementing, testing, reviewing, and merging a single GitHub issue. It manages each phase sequentially within an orchestrator-driven session to minimize context switching.

Track GitHub issue progress by maintaining an issue-progress.json file with a strict schema and top-level phase field. The automation updates this file at every phase to provide environment-aware progress tracking throughout the lifecycle.

Yes, single-issue workflows require an orchestrator to drive the session. The orchestrator processes issues one-by-one, enforcing per-phase orchestration with mandatory environment handling and agent interactions across the dev-lifecycle.

Yes, automating feature branch creation and pull requests for a single issue is the core function. The workflow spawns a feature branch, generates a plan, implements changes, runs tests, and merges the pull request upon successful completion.

Automated single-issue lifecycle management processes one issue per fresh session and enforces a strict issue-progress.json schema. It is designed for sequential per-phase orchestration rather than parallel multi-issue batch processing.