--- allowed-tools: Bash(git log: ), Bash(git diff: )…
Community ralph loop for ci, sourced from github. Verified exit condition, evaluator-gated.
--- allowed-tools: Bash(git log: ), Bash(git diff: ), Bash(git status: ), Bash(git branch: ), Bash(git push: ), Bash(gh pr create: ), Bash(gh pr view: ) description: Create a pull request targeting the correct branch per project conventions argument-hint: Optional PR title or description hint --- ## Context - Current branch: ! git branch --show-current - Commits ahead of main: ! git log --oneline origin/main..HEAD - Commits ahead of dev: ! git log --oneline origin/dev..HEAD - Changed files: ! git diff --name-only origin/main..HEAD - Git status: ! git status --short ## Your task Create a pull request following Tunarr's branching conventions: Branch targeting rules: - fix commits → target main - feat commits and large changes → target dev - If the commits are mixed or ambiguous, ask the user which branch to target before proceeding Steps: 1. Determine the correct target branch from the commit types above 2. If there are uncommitted changes, stop and tell the user to commit first 3. Push the current branch to origin if not already pushed 4. Draft a PR title and body based on the commits and diff: - Title: concise, follows conventional commit style - Bo
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