issue-pipeline

Yes, you can automate end-to-end issue triage by invoking the pipeline with specific issue numbers. It builds a dependency DAG, assigns execution order, and posts assessment, plans, and results directly to the repository.

Dependency-driven execution builds a dependency DAG from input issue numbers to map inter-issue relationships, assign execution order, and orchestrate PRs across chains. It posts explicit skip reasons to the repository when blocked.

Yes, the pipeline loads contextual guidance directly from the repository's prompts and templates to drive autonomous work. This guides the implementation, review, and fix phases while respecting out-of-scope constraints and safety checks.

The best way to process multiple related GitHub issues is to invoke the pipeline with multiple issue numbers. It handles triage, planning, implementation, and review, preserving an execution plan and reviews in repository documentation for accountability.

The automated issue pipeline skips certain issues when blocked by dependencies or safety checks. It posts explicit skip reasons to the repository, ensuring transparency and traceability for why specific issues could not be processed.