--- description: "Executes full autonomous engineering workflow with…
Community ralph loop for testing, sourced from github. Verified exit condition, evaluator-gated.
--- description: "Executes full autonomous engineering workflow with verification. Use when implementing complete features, tackling GitHub issues, or running end-to-end development cycles." model: opus argument-hint: "GitHub issue number/URL or feature description" allowed-tools: Bash(gh issue view: ), Bash(gh search: ), Bash(gh issue list: ), Bash(gh pr create: ), Bash(gh pr view: ), Bash(bundle exec: ), Bash(git: ), Read, Write, Edit, Glob, Grep, Agent --- # LFG - Full Autonomous Workflow Execute a complete engineering workflow with verification at each phase. ## Phase 0: Branch Setup BEFORE any other work, prepare the git branch: 1. Check the current branch: git branch --show-current 2. If NOT on main , switch: git checkout main 3. Pull latest: git pull origin main 4. Create feature branch: git checkout -b issue-{number}-{brief-description} (or feature/{description} if no issue number) --- ## Phase 1: Understand ### Step 1: Gather Requirements If $ARGUMENTS is a GitHub issue number or URL: bash gh issue view <number> --json title,body,labels,assignees,comments If $ARGUMENTS is a description, use it directly. ### Step 2: Define Acceptance Cr
claude-code
More testing loops
Ship the release
Run tests and update changelog until both pass without altering the public API.
/goal ship the release --success "tests pass and changelog updated" --constraints "do not touch the public API" --mode ordered
testingmedium risk
/ralph-loop "fix all tests" --max-iterations 5 (iterates until…
Community ralph loop for testing, sourced from github. Verified exit condition, evaluator-gated.
/ralph-loop "fix all tests" --max-iterations 5 (iterates until passing
testingmedium risk
Trim what loads before first paint
Reduce the data downloaded before the first screen appears, with tests and screenshots guarding behavior and appearance.
Reduce the data [web app] downloads before its first screen appears. First record passing tests, mobile and desktop screenshots, and compressed transferred bytes—the data actually downloaded. Use the build report only to suggest candidates. Defer, compress, or remove one item, then rebuild and rerun every check. Keep it only if tests pass, screenshots are pixel-identical, and bytes decrease; otherwise revert. Stop when no safe candidate remains, progress stalls, or approval is needed. Return measurements, changes, and untested states.
testingmedium risk