Automates dev loop: syncs git main, runs tests (Python/pytest/Django, JS/npm, Rust/cargo, Go), creates GitHub issues for failures, triages/prioritizes issues for TDD fixes.
npx claudepluginhub laurigates/claude-plugins --plugin github-actions-pluginThis skill uses the workspace's default tool permissions.
Automated development loop with issue creation, TDD, and CI monitoring.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Automated development loop with issue creation, TDD, and CI monitoring.
git branch --show-currentgit status --porcelainfind . -maxdepth 1 \( -name "package.json" -o -name "Cargo.toml" -o -name "pyproject.toml" -o -name "go.mod" -o -name "manage.py" \) -type fgh issue list --state open --limit 5 --json number,title --jq '.'Parse from $ARGUMENTS:
--max-cycles <n>: Limit to N issue resolution cycles (default: unlimited)--focus <bug|feature|test>: Only work on issues with matching label--quick-wins: Only pick issues estimated < 30 minutes--test-only: Only create issues for test failures; skip implementation--dry-run: Explain what would be done without making changesExecute this automated development loop:
1. Ensure on main branch and sync
git switch main
git pull
2. Run the project's test suite
manage.py, package.json, Cargo.toml, etc.)python manage.py testnpm testcargo testpytest or python -m pytestgo test ./...3. Create GitHub issues for any test failures
github:create_issue with:
"Test failure: {test_name}"["bug", "test-failure"]4. List current repository issues
github:list_issues with state=openSelect issues using this priority order:
priority: critical or bug + high prioritygood first issue or estimated < 1 hourtechnical-debt or refactorSelection criteria (must meet ALL):
blocked or waiting-for-inputIf no suitable issues found:
npm audit, pip-audit, cargo audit)For the selected issue, repeat until CI passes:
5. Create feature branch
git switch -c fix/issue-{number}-{brief-description}
6. Gather implementation context
context7:resolve-library-id followed by context7:get-library-docs for any tools mentioned7. Implement solution using TDD
8. Commit changes
git add <files>
git commit -m "fix: resolve issue #{number} - {brief description}"
9. Push branch
git push origin fix/issue-{number}-{brief-description}
10. Create pull request
github:create_pull_request with:
"fix: resolve issue #{number} - {brief description}""Fixes #{number}" plus description of changes11. Monitor CI status
12. Fix CI failures (if any)
github:get_pull_request_status to check specific failures13. Verify CI success
14. Close the issue
github:update_issue to close with state closed15. Return to Step 1
Handle these command variations:
/workflow:dev - Run continuous loop until stopped/workflow:dev --max-cycles 3 - Limit to 3 issue resolution cycles/workflow:dev --focus bug - Only work on issues labeled "bug"/workflow:dev --quick-wins - Only pick issues estimated < 30 minutes/workflow:dev --test-only - Only create issues for test failures; implementation handled separately/workflow:dev --dry-run - Explain what would be done without making changesIssue too complex to complete:
"This issue requires more detailed analysis - skipping for now"needs-investigationPersistent CI failures (3+ attempts):
"CI Pipeline Issue: {workflow_name} failing"ci-infrastructureNo issues available:
npm update, pip install --upgrade, etc.)Git/GitHub API errors:
After each completed issue, report:
โ
Issue #{number} resolved successfully!
Branch: fix/issue-{number}-{description}
PR: #{pr_number} - {pr_title}
CI Status: โ
All checks passing
Time: {duration}
Continuing to next issue...
Stop the loop when:
--max-cycles limit reachedProvide final summary:
๐ DevLoop completed!
๐ Summary:
- Issues resolved: {count}
- PRs created: {count}
- Tests added/fixed: {count}
- Total time: {duration}
๐ Recommendations:
- Review open PRs for merge
- Consider upgrading dependencies
- Add more test coverage for uncovered code
Required tools:
Repository requirements:
Best practices: