Post-push follow-up for a Pull Request or Merge Request: poll Continuous Integration (CI) checks, greptile threads, and the summary; fix what your diff broke; stop after two empty polls with CI green. Forge-aware (gh, glab). Use after creating or pushing to a…
Author a milestone or workstream spec that ships as a deterministic, review-clean Pull Request — intent capture first, file mechanics last. Use on "create a spec", "new milestone", "spec out X", "start M{N}_{NNN}", or any TODO.md attempt (forbidden — every…
Service-layer integration tests against real dependencies — Postgres, Redis, full HTTP router and middleware — with failure injection, per-test isolation, and leak audits. Use for handlers, repositories, services, or any real input/output module boundary; not…
Risk-weighted, failure-injecting unit tests across Python, TypeScript, React, Zig, Rust, and shell: behaviour, failure, invariant, and regression coverage behind a Definition-of-Done gate. Production-safety proofs live in the body. Use during implementation,…
Replies once to a live acceptance steer message without tools or credentials.
Woken for one concrete production incident, it reads telemetry, repository history, and the code itself at a verified head, authors the complete forward fix, and ships it as exactly one branch and one draft Pull Request via the GitHub API. The write token…
Verifies whether production evidence cleared a repaired incident by reading Grafana, Elasticsearch, and the exact merged GitHub commit.
Reviews GitHub pull requests and posts review comments.