--- allowed-tools: Bash(git branch: ), Bash(git status: )…
Community ralph loop for testing, sourced from github. Verified exit condition, evaluator-gated.
--- allowed-tools: Bash(git branch: ), Bash(git status: ), Bash(git log: ), Bash(git diff: ), Bash(git fetch: ) --- # Commit, review, push, pull request ## Git Context (Precomputed) - Fetch : ! git fetch origin develop 2>/dev/null || echo "(fetch failed)" - Current branch : ! git branch --show-current - Staged files : ! git diff --cached --name-only - Unstaged changes : ! git status --short - Recent commits : ! git log --oneline -5 ## Usage /cpp [in branch <branch-name>] ## Description Commits the current changes, performs a code review, applies fixes if needed, then pushes to remote and creates a pull request. ## Optional Arguments - in branch <branch-name> - Specifies the target branch to use for the commit, push, and PR ## Workflow ### 0. MANDATORY: Verify Correct Branch ALWAYS check the branch before any commit operations: 1. If task name/ID is known (from conversation context, branch name pattern, or user mention): - Fetch the Linear issue using linctl CLI: bash linctl issue get IOS-XXXX --json | jq -r '.gitBranchName' - Compare with current branch ( git branch --show-current ) - If mismatch: STOP
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