bang9

Triage unresolved PR review threads via webform and dispatch fixes through whip-start. Use after receiving review feedback on your own PR.

Triage unresolved PR review threads via webform and dispatch fixes through whip-start. Use after receiving review feedback on your own PR.

Systematic debugging loop — reproduce, analyze root cause, fix, then challenge with a fresh verification pass to distinguish fundamental fixes from workarounds. Use when debugging issues or when unexpected behavior needs a methodical approach.

Run multi-agent simulations to measure output consistency. Use when you want to A/B test, validate behavioral equivalence, or stress-test non-deterministic behavior at scale.

Systematic debugging loop — reproduce, analyze root cause, fix, then challenge with a fresh verification pass to distinguish fundamental fixes from workarounds. Use when debugging issues or when unexpected behavior needs a methodical approach.

Iterative review-fix loop — dispatch a fresh codex reviewer each round, apply fixes, repeat until LGTM. Use when you want rigorous code quality validation before merge.

Run multi-agent simulations to measure consistency of non-deterministic behavior. Use when the user wants to A/B test, validate behavioral equivalence, or stress-test outputs at scale.

Iterative review-fix loop — dispatch a fresh codex reviewer each round, apply fixes, repeat until LGTM. Use when you want rigorous code quality validation before merge.

Use when the user explicitly runs /setup-precommit to install or refresh a quiet, staged-only git pre-commit hook (secretlint → oxlint → oxfmt) wired through package.json "prepare". User-invoked command only, never auto-triggered.

Use when the user asks to create, make, or start a new branch (e.g. `/branch`), or wants a conventional-commit-style branch name generated from the current work.

Use when auditing or improving an agent skill package before it ships or is handed off.

Use when the user is working on their own PR — drafting/creating it, handling reviewer comments, verifying fixes, or requesting re-review.

Use when reviewing someone else's PR at any stage of the review lifecycle — digest a PR, write a review, or verify follow-up changes.

Use when fixing a bug, refactoring existing code without changing its behavior, or adding a feature that extends existing behavior — any code change that needs a verifiable foundation before the change is made.

Use when the user wants to A/B test prompts or workflows, validate behavioral equivalence, or stress-test non-deterministic outputs at scale via repeated multi-agent runs.

Use when the user wants to receive mail at a custom-domain address — a vanity or feedback address like hello@yourdomain.com or feedback@yourdomain.com — without hosting a mailbox, by forwarding it to a real inbox via Cloudflare Email Routing (free, receive/forward only). The domain must already be on Cloudflare. Triggers: "cloudflare 이메일 포워딩", "커스텀 도메인으로 메일 받기", "feedback@도메인 만들기", "email routing 셋업", "vanity email forwarding".

Use when a solo builder wants to stand up a Cloudflare Workers API server from an empty folder through local dev to production — pnpm monorepo, Hono, D1 + drizzle, zod contracts, oxc (oxlint/oxfmt), vitest, wrangler-only (no extra IaC). Triggers: "Cloudflare Workers API 셋업", "Hono + D1 백엔드 만들기", "wrangler 프로젝트 셋업", "D1 drizzle 마이그레이션 세팅", "worker API 배포까지".

Use when a solo builder wants to set up a new React Native / Expo app's external services before its first release — EAS + Android signing credentials, a Firebase/GCP project, standalone Google Sign-In OAuth clients, and a Google Play Console app. Triggers: "RN/Expo 앱 셋업", "expo 앱 초기 세팅", "EAS 프로젝트 만들기", "Google Sign-In 셋업", "Firebase + GCP + Play Console 연결".