Claude Code skills plus scheduled GitHub agents automate review and triage
At a glance
An HN commenter described a Claude Code setup with reusable skills for a UI library/Storybooks/APIs, a post-change review agent, PR checklist reviews, scheduled docs/coverage agents, and ticket triage that leaves a halfway-done plan on each issue. This workflow is listed under Claude-Code, Code-Review, CI, Agent-Tooling.
CircleCI's Chunk sidecars run scoped microbuilds in Firecracker/E2B microVMs that mirror CI, hooking agent stop/eval events so Claude Code, Codex, or Cursor changes are validated before commit—~27s microbuilds and 3–5× lower token burn on retries in their tests.
Kelos orchestrates Claude Code, Codex, Gemini, or OpenCode in ephemeral Kubernetes pods as CRDs—watching bug issues, drafting fix PRs, self-reviewing, and retrying when CI fails—while the author still does final review and merge.
Room Service 3.3’s local MCP gives coding agents disk/port/Git visibility and actions like stop-port or trash build data—off by default, local socket only, permanent actions need in-app approval, every action logged.
Show HN: Statewright's Rust engine enforces plan/implement/test states for Claude Code (and other CLIs) via MCP hooks—wrong tools are blocked structurally, shrinking death spirals for both small and frontier models.