chachi-shell

Reviews a GitHub PR and creates a pending review with editorially gated inline/body findings. Use when the user asks to review a PR or create a draft GitHub review.

Load machine-local rule overrides for a given skill from the shared ~/.agents skills directory.

Create one or more atomic commits from current changes, grouping by logical unit

Create a JIRA ticket interactively — gathers requirements through conversation, proposes the ticket, and creates it after approval

Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.

Compact the current conversation into a handoff document for another agent to pick up.

Find deepening opportunities in a codebase, informed by the domain language in .agent-state/CONTEXT.md and the decisions in .agent-state/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.

Mark the issue currently being worked on as done. Use ONLY when the user explicitly says "/issue-done", "mark done", or "this issue is done". Do not auto-invoke when the user merely finishes a task or says "done" in passing.

Push current branch to remote and create or update a draft PR

Complete a git rebase, resolving conflicts along the way

Switch the assistant to a slower, more deliberate communication mode — short questions, no long messages, one thing at a time. Use when user says "slow down", "slowdown", "/slowdown", "ask one question at a time", "shorter messages", or asks for less verbose interaction.

Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.

Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.

Coding standards to follow when writing or modifying code in any project

Documentation standards to follow when creating or updating component docs in any project

Testing standards to follow when writing or modifying tests in any project

Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.

Ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman.

Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.

Compact the current conversation into a handoff document for another agent to pick up.

Find deepening opportunities in a codebase, informed by the domain language in .agent-state/CONTEXT.md and the decisions in .agent-state/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.

Mark the issue currently being worked on as done. Use ONLY when the user explicitly says "/issue-done", "mark done", or "this issue is done". Do not auto-invoke when the user merely finishes a task or says "done" in passing.

Switch the assistant to a slower, more deliberate communication mode — short questions, no long messages, one thing at a time. Use when user says "slow down", "slowdown", "/slowdown", "ask one question at a time", "shorter messages", or asks for less verbose interaction.

Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.

Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.

Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.

Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.

Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.