Overview
GemKit provides slash commands that trigger structured workflows for common development tasks. These commands are defined in .gemini/commands/ and orchestrate agents with predefined patterns for consistent, high-quality results.
Available Commands
| Command | Description | Use Case |
|---|---|---|
/cook | Implement a feature step by step | New features, guided implementation |
/code | Start coding & testing an existing plan | Execute planned work |
/test | Run tests and analyze results | Testing and coverage analysis |
The /cook Command
The /cook command guides you through implementing a feature step by step. It's ideal when you want a structured, interactive approach to building new functionality.
Usage
Or within an agent session, simply type:
How It Works
- Understand - Analyzes the feature request and codebase context
- Plan - Creates a step-by-step implementation plan
- Implement - Guides you through each step with code generation
- Verify - Checks implementation against requirements
Example
The agent will:
- Research form best practices
- Plan the component structure
- Implement form fields with validation
- Add error handling and success states
- Guide you through testing
The /code Command
The /code command executes implementation when you already have a plan. It's optimized for following existing specifications or continuing planned work.
Usage
How It Works
- Load Plan - Reads existing plan or specification
- Execute - Implements according to the plan
- Test - Runs tests to verify implementation
- Report - Summarizes what was completed
Example
Difference from /cook
| Aspect | /cook | /code |
|---|---|---|
| Approach | Interactive, step-by-step | Direct execution |
| Best for | Exploratory development | Planned implementation |
| Guidance | High - guides each step | Low - executes plan |
| Input | Feature description | Existing plan/spec |
The /test Command
The /test command runs tests and provides analysis of the results, including coverage reports and failure diagnostics.
Usage
How It Works
- Identify - Finds relevant test files
- Execute - Runs the test suite
- Analyze - Parses results and coverage
- Report - Provides actionable insights
Example
Command Configuration
Commands are defined in .gemini/commands/ as TOML files:
Command Structure
Each command TOML file defines:
- Command name and description
- Default agent to use
- Required skills
- Execution steps
Using Commands with Agents
Basic Usage
Combining Commands with Skills
Best Practices
When to Use /cook
- Building new features from scratch
- Learning a new codebase
- Exploratory development
- When you want step-by-step guidance
When to Use /code
- Executing well-defined plans
- Following specifications
- Batch implementation
- CI/CD automated tasks
When to Use /test
- After implementing features
- Coverage analysis
- Debugging test failures
- Pre-commit verification
Creating Custom Commands
You can create custom commands by adding TOML files to .gemini/commands/:
Then use it:
Related Documentation
gk agent- Agent management and spawninggk plan- Plan management- Skills Reference - Available skills
- Agents Guide - Understanding agents