kenryu42

Restate the last message in plain human language, with no jargon.

Improve repository test coverage with autonomous, test-only quick wins. Run `bun run test:coverage`, inspect coverage artifacts, add tests that exercise real production behavior, repeat until no quick wins remain, validate the result, and report opportunities…

Manual multi-agent build workflow — Fable owns judgment (plan, investigate, design, review, decide), Opus owns execution (implement, fix, validate); a Fable planner designs a task-specific stage plan, then a Fable review + Opus fix loop closes it out.

Delegate substantial implementation, fixing, code exploration, rebasing, and PR landing mechanics to Codex CLI while Claude handles design, decisions, review, and verification.

Pre-commit/ship code review: Codex default; optional Claude or Pi.

Create a coherent Conventional Commit with concise, high-signal context. Use when the user explicitly asks to commit current work or invokes $commit-with-context. Keep unrelated changes out and avoid splitting one task into artificial micro-commits.

Find and verify potential sponsors for a GitHub repository by mining GitHub README sponsorship placements. Use when the user provides a target GitHub repo URL and wants sponsor leads, README sponsor discovery, sponsor verification, contact URLs, or a…

Use when the user asks for Codex Security workflows: repository-wide or scoped-path security scans, security reviews of pull requests, commits, branch diffs, or working-tree patches, deep exhaustive repository scans, fixing validated or plausible security…

Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform. Use for /create-verification-skill, "make a control skill for this repo", or when a project has no scripted way to prove…

Periodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session driving every feature, at most one PR of proven corrections. Use for /maintain-verification-skill or "audit the verify skill".

Pre-commit/ship code review: Codex default; optional Claude or Pi.

Watch an open PR on this repo — fix failing CI, wait out the review bots (coderabbitai, greptile-apps, pullfrog), handle the straightforward findings, and drive the PR to a mergeable state without re-prompting.

Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up. Use for 'blast radius of X', 'what could this break', or reviewing a small diff you…

Create a coherent Conventional Commit with concise, high-signal context. Use when the user explicitly asks to commit current work or invokes $commit-with-context. Keep unrelated changes out and avoid splitting one task into artificial micro-commits.

Analyze GitHub issues (bugs or feature requests)

Find and verify potential sponsors for a GitHub repository by mining sponsor data from peer repos: README sponsor sections, sponsorkit SVGs, the GitHub Sponsors API, and Open Collective. Use when the user provides a target GitHub repo URL and wants sponsor…

Launch and drive the real cc-safety-net CLI — the hook decision path, explain, status/doctor, logs, and the local policy GUI — against an isolated home, capturing evidence. Use when a change needs proof in the running app, not just the test suite.

Operate CC Safety Net: explain why a command was blocked, triage false positives, configure custom rulebooks, manage agent CLI integrations, and diagnose protection.

Generate and publish concise, evidence-based notes in the body of the latest existing GitHub Release. Use only when the user explicitly invokes `$release-notes` or explicitly asks to update the latest existing GitHub Release body. Do not invoke for general…

Use when working in the cc-safety-net repo to find non-obvious simplification candidates: dead, duplicated, speculative, over-built, or contract-exceeding surfaces in the analyzer, rules, guards, integrations, CLI, or GUI. Produces evidence-backed proposals…

Configure cc-safety-net custom rules.

Verify cc-safety-net custom rules.

Sync the docs with the cc-safety-net source repo. Drafts page updates from the source drift, validates them, then advances SOURCE-SYNC.json and commits automatically.