--- allowed-tools: Bash(git pull: ), Bash(git push: )…
Community ralph loop for ci, sourced from github. Verified exit condition, evaluator-gated.
--- allowed-tools: Bash(git pull: ), Bash(git push: ), Bash(git status: ), Bash(git stash: ), Bash(git log: ), Bash(git fetch: ) description: Sync agent state with remote repository (pull then push) --- # Sync Agent State Synchronize the local agent state with the remote GitHub repository. ## Context - Current branch: ! git branch --show-current - Remote tracking: ! git status -sb - Pending commits: ! git log --oneline origin/main..HEAD 2>/dev/null || echo "No remote tracking yet" ## Instructions ### Step 1: Fetch and Check Status bash git fetch origin git status ### Step 2: Pull Changes (with rebase to keep history clean) bash git pull --rebase origin main If conflicts occur: 1. List the conflicting files 2. Show the conflict markers 3. Ask the user how to resolve (keep ours, keep theirs, or manual) 4. After resolution: git add <resolved-files> then git rebase --continue ### Step 3: Push Local Commits bash git push origin main If push fails (rejected due to remote changes): 1. Pull again with rebase 2. Resolve any new conflicts 3. Push again ## Safety Checks - Never force push ( git push --force ) without explicit user approval -
claude-code
More ci loops
Fix CI, ship the PR
Check your PR's CI status and fix failures until the build passes.
/loop 5m check my PR and fix CI , /schedule |
cimedium risk
Ship specs through code review
Run spec-driven workflow loop every 10 minutes: plan work, collect reviews, execute tasks, open pull requests.
/loop 10m /flow-next:pilot # build loop: ready spec → plan → reviews → work → draft PR
cimedium risk
--- allowed-tools: Bash(git checkout --branch: ), Bash(git status…
Community ralph loop for ci, sourced from github. Verified exit condition, evaluator-gated.
--- allowed-tools: Bash(git checkout --branch: ), Bash(git status: ), Bash(git commit: ), Bash(gh pr create: ), Bash(pre-commit), Edit, Read, Write description: Prepare and commit the code already added to git --- Run pre-commit to find any outstanding problems with the changes already added to git. Once they are taken care of, you may git add only the original files I already added to re-run pre-commit. DO NOT add any other files to git. When pre-commit passes, commit the code. Don't use 'pre-commit run --all-files' to validate the code, just run 'pre-commit' to run it on files that are already git added. Add them before running pre-commit if you have made changes. If black says it reformatted a file, add it and then re-run pre-commit
cimedium risk