--- description: Commit all changes, push branch, create/update…
Community ralph loop for ci, sourced from github. Verified exit condition, evaluator-gated.
--- description: Commit all changes, push branch, create/update PR, and run local validation allowed-tools: Bash(git rev-parse: ), Bash(git status: ), Bash(git add: ), Bash(git commit: ), Bash(git push: ), Bash(gh pr view: ), Bash(gh pr create: ), Bash(scripts/local-validate.sh: ), Bash(./scripts/ship-pr.sh: ), Read argument-hint: ["<commit message>"] ["<pr title>"] ["<pr body>"] --- Run the one-shot ship flow from this repository: 1. Commit all files. 2. Push current branch. 3. Create PR if missing (or reuse current branch PR). 4. Run local validation. 5. Push again if validation auto-created a commit. ## Command Use: bash ./scripts/ship-pr.sh $ARGUMENTS ## Notes - This command refuses to run on main / master by design. - You can run plain /ship with no arguments. - If args are omitted, commit message / PR title / PR body are auto-generated from changed files and branch. - Set SHIP BASE BRANCH=... before running if you need a base branch other than main
claude-code
More ci loops
Morning-triage harness with adversarial reviewer
A cron-fired skill that finds its own work (failed CI, new issues, recent commits), fans each finding out to an isolated worktree, gates every fix behind an adversarial reviewer that assumes the code is broken, and leaves draft PRs — merging stays human.
# .claude/skills/morning-triage/SKILL.md — fired by cron at 06:00
READ (discovery inputs): CI runs that failed since the last run (gh run list --status failure); issues opened in the last 24h; commits merged since yesterday; the previous ./state/triage.md.
JUDGE: for each candidate decide actionable NOW vs noise; blocks a release → P0; already tracked → skip. Keep only what is worth a worktree today — the loop picks, you don't hand it a list.
WRITE: append findings (finding | source | priority | status) to ./state/triage.md and commit it so tomorrow's run can read it.
HANDOFF: one git worktree per finding (git worktree add ../wt-<slug> -b fix/<slug>), MAX_PARALLEL=3 — capped by how many PRs a human can actually review, not by the machine.
VERIFY: a second subagent as adversarial reviewer — ROLE: adversarial code reviewer. ASSUME this code is BROKEN until proven otherwise; do not praise. CHECK in order: does it run (execute, don't read); run the tests and paste real output; edge cases the author skipped; does behavior match the ticket. VERDICT: PASS only if every check holds, otherwise REJECT with each reason listed. Maximum 3 attempts per finding, then log as blocked.
STOP (red lines): never merge, never delete, never push to main; anything uncertain goes to ./inbox/ for a human, NOT into a PR. Caps set before the first run: per-run timeout 45 minutes, daily budget $20. PRs open as drafts; merging stays human.
cimedium risk
--- description: Format code, stage changes, and create…
Community ralph loop for ci, sourced from github. Verified exit condition, evaluator-gated.
--- description: Format code, stage changes, and create a pull request allowed-tools: - Bash argument-hint: [base-branch] --- # Prepare and create pull request First, let me run the formatting script: ! bash scripts/format.sh Now let me check what files were modified: ! git status --short Let me also check if there's a CLAUDE.md with PR instructions: @CLAUDE.md ## Steps to create PR: 1. Review the changed files listed above and determine which ones are related to our current work 2. Stage only the relevant files - I'll ask you to confirm which files to stage if there are unrelated changes 3. Determine the base branch : - If you provided an argument: use $1 - Otherwise, I'll ask you to confirm if it should be develop (the usual default) or another branch 4. Create the PR using the gh CLI tool according to any instructions in CLAUDE.md 5. Ask you for : - PR title (if not obvious from the changes) - PR description (I'll draft one based on the changes) Let's proceed! Based on the git status above, which files should we stage for this PR?
cimedium risk
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