Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
Pre-push Claude-driven code review loop with auto-fix. Runs parallel review agents (CLAUDE.md, bugs, git history, code comments, security, test coverage, and — on substantial diffs — structural simplification and observability coverage; plus, in cycle 1 on feature work, an intent-reconciliation agent that models what the PR should do from its purpose and reconciles that against the code to catch omission bugs) per cycle, scores each finding 0-100 with an independent Haiku rater, auto-fixes ≥80 findings, asks about 50-79 in a single batch per cycle, and stores per-repo learnings in .git/info/. Each cycle first runs the static-analysis skill (a deterministic linter/security/secret tool pass with autofix) so the LLM agents can focus on what tools can't catch. On clean exit, a final manual-testing evidence gate verifies the PR carries proof the changed functionality actually works — and produces that proof itself (local dev servers + playwright + surge-image-upload) when missing — reconciles the PR description to
Run every applicable static-analysis tool on a repo — detect languages/configs, run the curated CodeRabbit-weighted analyzer set (installed or ephemerally via npx/uvx), and write results to .static-analysis/. Use when asked to run static analysis, lint the whole repo, run all linters/analyzers, do a code-quality/security scan, or check a repo before pushing. Report-only by default; --fix opts into safe autofixers. Subagent-safe (never blocks).
Drive a pull request to a mergeable state: no conflicts with the base branch, green CI, and a clean review. Integrates the base branch and resolves conflicts, delegates PR feedback resolution (human + bot/CodeRabbit) to the resolve-feedback skill, runs the local review loop, fixes failing CI (via the fix-ci skill), and pushes. Waits once for CodeRabbit's initial automatic review to land and resolves its feedback, but does not re-request reviews or wait for CodeRabbit again after later pushes (CodeRabbit reviews each PR once, on open). Use when the user wants to drive a PR forward / get it to green / make it mergeable, resolve PR comments or review feedback, fix CI, or resolve merge conflicts — even if there is no feedback yet. Drives to mergeable but does NOT merge.
Retrieve, classify, and resolve PR review feedback — inline review threads, review summaries, and generic PR comments, from humans and bots. Fixes valid feedback (committing locally), posts justifications for invalid feedback, files follow-ups for out-of-scope items, and — critically — literally marks each item resolved/dismissed on GitHub (a reply is NOT a resolution). Supports an interactive mode (prompts on human feedback) and a non-interactive/batch mode (auto-applies bot/procedural feedback, defers human feedback to the caller). Use when the user wants to resolve PR feedback / review comments / review threads, address reviewer comments, or 'resolve feedback'. This is the feedback engine that the drive-pr and pr-triage skills delegate to; it does not push, run the review loop, fix CI, or integrate the base branch — that is the caller's job.
Audit and sync all pending changes across the dotfiles and dotprivate bare repos. Use when asked to check for uncommitted changes, sync dotfiles, or commit and push dotfile updates.
Generate a summary of GitHub activity for a configured client team. Shows PRs and issues each team member has been involved with. Default is last 7 days; specify a number of days to change the lookback period. Use when asked about team activity, what people have been working on, or to get a status update. Client configs live at ~/.claude/skills/client-report/clients/.
Analyze GitHub Actions usage for a GitHub org and identify ways to cut billable minutes. Estimates billable minutes per workflow (private repos only — public repos run free), ranks the biggest cost drivers, compares CI vs Copilot review, and recommends concrete efficiency fixes. Use when asked which CI checks use the most minutes, how to reduce Actions costs/usage, why CI won't start (budget/minutes block), or for a periodic Actions spend review. Accepts an org name.