Loading...
Loading...
Found 20 Skills
When GitHub Actions fails, fetch failing job logs and assign each failing job to a separate subagent that fixes its slice of the problem in parallel. Use for multi-job CI failures where jobs are independent.
Set up automated CI failure detection and fixing using Claude Code. Use when you want to create a GitHub Actions workflow that automatically analyzes workflow failures, applies fixes for common issues, and opens issues for complex problems.
Use when monitoring a PR (or a full Graphite stack of PRs) that needs CI fixes or review comment responses. Runs as a long-running session with intelligent sleep intervals. Handles failing checks, reviewer feedback, and pushes verified fixes autonomously.
Triage and fix failing Buildkite CI checks for RisingWave pull requests by extracting concrete failing tests, diffs, and error messages from Buildkite build/job logs and artifacts, then applying focused code or test fixes. Use when users ask to diagnose red Buildkite checks, investigate flaky/failing CI jobs, understand why a Buildkite build failed, or provide Buildkite/GitHub check URLs and want a concrete fix.
Fixes broken typing checks detected by ty, make typing, or make check-repo. Use when typing errors appear in local runs, CI, or PR logs.
Drive a PR to mergeable state — check CodeRabbit and reviewer comments, address valid ones, reply and resolve invalid ones, fix CI failures (even pre-existing ones from main), push fixes, then loop every 4.5 minutes until two consecutive clean checks. Use after opening a PR when you want it babysitted to green.
Keeps an open GitHub PR moving to merge: detects the PR from the current branch, watches for merge conflicts, red CI (GitHub Actions, Buildkite, Vercel, Fly.io), inbound review comments, and merge readiness, fixes what is safe, and reports only state changes. Also runs one-shot: diagnose and fix CI, rebase and resolve conflicts, or triage and answer review comments. Use when asked to "babysit a PR", "watch this PR", "keep the PR green", "fix CI", "why is CI red", "resolve conflicts", "rebase onto main", "address the review comments", "reply to the reviewers", "is this PR ready to merge", or "what is blocking the merge". For opening or editing the PR use pr-creator; for reviewing the local diff use pr-reviewer; for applying a pr-reviewer report use tidy; for npm release PRs use autoship.
Find failing PR checks, inspect logs or external check links, and apply focused fixes