kirei

Set up production-ready Sentry error + performance monitoring for a project. Detects the framework (Electron, Next.js, Vite/React SPA, Node/Nest, React Native), asks the consent + scope + region decisions, verifies the current SDK API via Ref, then spawns the kirei-sentry agent to produce a framework-specific plan and kirei-forge to implement it — with consent gating, recursive PII scrubbing, CI-only source-map upload, region handling, and the exact CI secrets. Use whenever a user wants to add Sentry, set up error tracking / crash reporting, wire production monitoring, add performance tracing, or integrate Sentry into a new or existing project — even if they don't say "kirei". Invoke with /kirei-sentry; the skill asks the key decisions before working.

Orchestrate research + execution for any engineering task. Auto-detects task type (security, ui, refactor, perf, arch, test, migrate, review, debug, data, observability, bundle, license, error, eval, or general) and execute complexity (build vs forge), then spawns the right specialist research agent followed by the right execute agent. Use whenever the user asks to investigate, audit, fix, refactor, debug, optimize, review, or implement anything that benefits from research before code — even if they don't say "kirei". Pass --research-only to skip the execute step. Invoke with /kirei followed by a task description.

Audit a codebase for quality and maintainability — code smells, DRY violations, god files, dead code, inconsistent conventions, and unfollowed best practices. Depth-tunable like /kirei-deps; a scout pass sizes how many kirei-refactor agents run in parallel (1 → up to 6) to match the repo. Produces one merged, dependency-ordered cleanup plan, then offers to fix the issues in order via kirei-build / kirei-forge. Use whenever a user asks to audit the codebase, find code smells, hunt technical debt, check for DRY violations, find god files or dead code, surface inconsistencies, run a code-quality / health pass, or plan a refactor — even if they don't say "kirei". Invoke with /kirei-audit; the skill asks which depth before working.

Run multiple kirei research agents in parallel against the same target and merge their findings into one combined report. Use when a question needs more than one lens (e.g., "audit this module for security AND performance AND architecture", or "audit observability AND error handling together"). Invoke with /kirei-chain followed by a task description; optionally pass --types security,perf,arch to pin the lens set. Valid lenses: security, ui, refactor, perf, arch, test, data, observability, bundle, error, general.

Conversational pros/cons audit for an idea, feature, or project — before any code is written. Walks the user through problem framing, value, constraints, alternatives, risks, and a recommended next step (kill / spike / build now / wait), then writes a structured decision doc to docs/discuss/. Use whenever the user says "I'm thinking about…", "should we build…", "is X a good idea", "let's talk through…", "what do you think about adding Y", "audit this idea", or wants to think through an approach before committing. Pairs with /kirei — the resulting doc can be passed back via /kirei --findings <path> if the user decides to proceed. Invoke with /kirei-discuss followed by an idea description.

Strip an existing JS/TS repo (Electron, Next.js, Vite, monorepo, etc.) down to a reusable starter template. Analyzes the codebase, splits the strip work into independent phases, and runs them via parallel sub-agents. Asks the user at invocation time about target directory, detection mode (user-marked paths / heuristic / keep-list), execution mode (parallel vs sequential), commit style (small conventional vs one-per-phase), co-author attribution, and whether to seed CLAUDE.md in the new template. Use whenever a user asks to "turn this repo into a template", "strip this for a starter", "make a boilerplate from this project", "templatize", "scaffold from existing repo", or "extract template". Invoke with /kirei-templatize followed by an optional task description.

Audit a project's dependencies for safety. Detects the package manager (pnpm/npm/yarn/bun/poetry/uv/cargo/go/bundler), runs its audit, fetches GitHub Dependabot alerts when available, and produces a depth-tunable report — quick CVE counts, safe-bump list, or full ordered upgrade plan with risky-major handoff to /kirei migrate. Use whenever a user asks to audit deps, check for CVEs, find safe upgrades, review Dependabot alerts, run npm/pnpm/yarn/bun audit, check for outdated packages, or plan a dependency hygiene pass — even if they don't say "kirei". Invoke with /kirei-deps; the skill will ask which depth before working.