dev-loop

Automating a pull request workflow involves creating a feature branch, running local lint and unit tests, opening a PR, and updating issue tracking status. dev-loop enforces this lifecycle while requiring human approval before merging.

Yes, automated branch creation and issue tracking support multi-repo projects. dev-loop resolves workspace members and coordinates deterministic branch naming and PR workflows across single-repo and multi-repo environments.

Enforcing a human review gate before merging requires an automated workflow that moves the issue status to In Review and halts subsequent actions. dev-loop implements two human gates to prevent unauthorized merges or marking issues as Done.

Generating self-review artifacts requires running local format, type-check, and integration tests, then storing the output reports. dev-loop produces these traceability artifacts and saves them under the .development/shared/reports directory.

Yes, automated issue lifecycle management supports cross-skill coordination. dev-loop integrates with issue-discovery, tracker-sync, release-tracker, and plan-keeper skills to update release umbrellas and plans during the PR workflow.

Local checks before opening a pull request include format, lint, type-check, unit, integration, and end-to-end tests where applicable. dev-loop automates this local review loop to ensure code quality before moving issues to In Review.