skills/autonomous-loops/SKILL.md
Patterns for autonomous agent loops — sequential pipelines, parallel generation, continuous PR loops, and de-sloppify passes. Use when setting up automated workflows, CI/CD agent loops, batch processing with Claude, or multi-agent orchestration. Covers loop architecture from simple sequential to RFC-driven DAG orchestration.
npx skillsauth add kitfunso/omniskill autonomous-loopsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Six loop architectures of increasing sophistication. Pick the simplest one that fits.
Each step is isolated (fresh context). Order matters, exit codes propagate.
claude -p "Implement auth module per spec in PLAN.md" && \
claude -p "Review changes, fix issues, run tests" && \
claude -p "Write commit message, commit"
Use when: Simple linear tasks, each step is independent.
Two focused agents beat one constrained agent.
claude -p "Implement feature X with full TDD"
claude -p "Review all changes. Remove: tests of language behavior, console.logs, dead code, over-engineering. Run test suite."
Use when: Any implementation task. Always follow implementation with cleanup.
Spawn N agents with different creative directions. Each gets an iteration number to prevent duplicates.
for i in $(seq 1 5); do
claude -p "Iteration $i: Generate solution for X. Be creative, try approach $i." &
done
wait
claude -p "Review all 5 solutions in output/. Pick the best, explain why."
Use when: Creative/exploratory tasks where multiple approaches might work.
Agent runs in a loop: create PR → wait for CI → fix failures → repeat.
Key elements:
SHARED_TASK_NOTES.md bridges context gaps between iterationsUse when: Automated PR workflows, CI-driven development.
Most sophisticated: decompose spec into tiered work units with dependency DAG.
Use when: Large features with multiple interdependent components.
Need strict CI/PR control? → Continuous PR loop
Need RFC decomposition? → DAG orchestration
Need exploratory parallel gen? → Parallel generation
Simple linear task? → Sequential pipeline
Any implementation task? → Always add de-sloppify pass
--max-budget-usddevelopment
Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas. Use when asked to "weekly retro", "what did we ship", or "engineering retrospective". Proactively suggest at the end of a work week or sprint.
development
Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Proactively suggest when the user says a feature is ready for testing or asks "does this work?". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary. For report-only mode, use /qa-only.
development
Report-only QA testing. Systematically tests a web application and produces a structured report with health score, screenshots, and repro steps — but never fixes anything. Use when asked to "just report bugs", "qa report only", or "test but don't fix". For the full test-fix-verify loop, use /qa instead. Proactively suggest when the user wants a bug report without any code changes.
testing
Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations. Use when asked to "review the architecture", "engineering review", or "lock in the plan". Proactively suggest when the user has a plan or design doc and is about to start coding — to catch architecture issues before implementation.