Commands Reference
Complete reference for all GemBoost commands and their usage
GemBoost Commands Guide
GemBoost provides 22 commands for Gemini Cli: /gb:*
commands for workflows and @agent-*
for specialists.
🎯 Understanding GemBoost Commands
How GemBoost Works
GemBoost provides behavioral context files that Gemini Cli reads to adopt specialized behaviors. When you type /gb:implement
, Gemini Cli reads the implement.md
context file and follows its behavioral instructions.
GemBoost commands are NOT executed by software - they are context triggers that modify Gemini Cli's behavior through reading specialized instruction files from the framework.
Slash Commands
/gb:*
Trigger workflow patterns and behavioral modes
Agent Invocations
@agent-*
Manually activate specific domain specialists
Flags
--think
, --safe-mode
Modify command behavior and depth
The Context Mechanism
/gb:implement "auth system"
~/.gemini/GemBoost/Commands/implement.md
Key Point: This creates sophisticated development workflows through context management rather than traditional software execution.
📝 Command Quick Reference
Command Type | Where to Run | Format | Purpose | Example |
---|---|---|---|---|
🖥️ Installation | Terminal/CMD | GemBoost [command] | Setup and maintenance | GemBoost install |
🔧 Configuration | Terminal/CMD | python3 -m GemBoost [command] | Advanced configuration | python3 -m GemBoost --version |
💬 Slash Commands | Gemini Cli | /gb:[command] | Workflow automation | /gb:implement "feature" |
🤖 Agent Invocation | Gemini Cli | @agent-[name] | Manual specialist activation | @agent-security "review" |
⚡ Enhanced Flags | Gemini Cli | /gb:[command] --flags | Behavior modification | /gb:analyze --think-hard |
Remember: All /gb:
commands and @agent-
invocations work inside Gemini Cli chat, not your terminal. They trigger Gemini Cli to read specific context files from the GemBoost framework.
Table of Contents
Essential Commands
Core workflow commands for immediate productivity:
/gb:brainstorm - Project Discovery
Purpose: Interactive requirements discovery and project planning
Syntax: /gb:brainstorm "your idea"
[--strategy systematic|creative]
Use Cases:
- • New project planning:
/gb:brainstorm "e-commerce platform"
- • Feature exploration:
/gb:brainstorm "user authentication system"
- • Problem solving:
/gb:brainstorm "slow database queries"
/gb:implement - Feature Development
Purpose: Full-stack feature implementation with intelligent specialist routing
Syntax: /gb:implement "feature description"
[--type frontend|backend|fullstack] [--focus security|performance]
Use Cases:
- • Authentication:
/gb:implement "JWT login system"
- • UI components:
/gb:implement "responsive dashboard"
- • APIs:
/gb:implement "REST user endpoints"
- • Database:
/gb:implement "user schema with relationships"
/gb:analyze - Code Assessment
Purpose: Comprehensive code analysis across quality, security, and performance
Syntax: /gb:analyze [path]
[--focus quality|security|performance|architecture]
Use Cases:
- • Project health:
/gb:analyze .
- • Security audit:
/gb:analyze --focus security
- • Performance review:
/gb:analyze --focus performance
/gb:business-panel - Strategic Business Analysis
Purpose: Multi-expert business strategy analysis with 9 renowned thought leaders
Syntax: /gb:business-panel "content"
[--mode discussion|debate|socratic] [--experts "name1,name2"]
Use Cases:
- • Strategy evaluation:
/gb:business-panel "our go-to-market strategy"
- • Competitive analysis:
/gb:business-panel @competitor_analysis.pdf --mode debate
- • Innovation assessment:
/gb:business-panel "AI product idea" --experts "christensen,drucker"
- • Strategic learning:
/gb:business-panel "competitive strategy" --mode socratic
Expert Panel: Christensen, Porter, Drucker, Godin, Kim/Mauborgne, Collins, Taleb, Meadows, Doumont
/gb:troubleshoot - Problem Diagnosis
Purpose: Systematic issue diagnosis with root cause analysis
Syntax: /gb:troubleshoot "issue description"
[--type build|runtime|performance]
Use Cases:
- • Runtime errors:
/gb:troubleshoot "500 error on login"
- • Build failures:
/gb:troubleshoot --type build
- • Performance problems:
/gb:troubleshoot "slow page load"
/gb:test - Quality Assurance
Purpose: Comprehensive testing with coverage analysis
Syntax: /gb:test
[--type unit|integration|e2e] [--coverage] [--fix]
Use Cases:
- • Full test suite:
/gb:test --coverage
- • Unit testing:
/gb:test --type unit --watch
- • E2E validation:
/gb:test --type e2e
/gb:improve - Code Enhancement
Purpose: Apply systematic code improvements and optimizations
Syntax: /gb:improve [path]
[--type performance|quality|security] [--preview]
Use Cases:
- • General improvements:
/gb:improve src/
- • Performance optimization:
/gb:improve --type performance
- • Security hardening:
/gb:improve --type security
/gb:document - Documentation Generation
Purpose: Generate comprehensive documentation for code and APIs
Syntax: /gb:document [path]
[--type api|user-guide|technical] [--format markdown|html]
Use Cases:
- • API docs:
/gb:document --type api
- • User guides:
/gb:document --type user-guide
- • Technical docs:
/gb:document --type technical
/gb:workflow - Implementation Planning
Purpose: Generate structured implementation plans from requirements
Syntax: /gb:workflow "feature description"
[--strategy agile|waterfall] [--format markdown]
Use Cases:
- • Feature planning:
/gb:workflow "user authentication"
- • Sprint planning:
/gb:workflow --strategy agile
- • Architecture planning:
/gb:workflow "microservices migration"
Common Workflows
Proven command combinations:
New Project Setup
/gb:brainstorm "project concept" # Define requirements /gb:design "system architecture" # Create technical design /gb:workflow "implementation plan" # Generate development roadmap
Feature Development
/gb:implement "feature name" # Build the feature /gb:test --coverage # Validate with tests /gb:document --type api # Generate documentation
Code Quality Improvement
/gb:analyze --focus quality # Assess current state /gb:improve --preview # Preview improvements /gb:test --coverage # Validate changes
Bug Investigation
/gb:troubleshoot "issue description" # Diagnose the problem /gb:analyze --focus problem-area # Deep analysis /gb:improve --fix --safe-mode # Apply targeted fixes
Full Command Reference
Development Commands
Command | Purpose | Best For |
---|---|---|
workflow | Implementation planning | Project roadmaps, sprint planning |
implement | Feature development | Full-stack features, API development |
build | Project compilation | CI/CD, production builds |
design | System architecture | API specs, database schemas |
Analysis Commands
Command | Purpose | Best For |
---|---|---|
analyze | Code assessment | Quality audits, security reviews |
business-panel | Strategic analysis | Business decisions, competitive assessment |
troubleshoot | Problem diagnosis | Bug investigation, performance issues |
explain | Code explanation | Learning, code reviews |
Quality Commands
Command | Purpose | Best For |
---|---|---|
improve | Code enhancement | Performance optimization, refactoring |
cleanup | Technical debt | Dead code removal, organization |
test | Quality assurance | Test automation, coverage analysis |
document | Documentation | API docs, user guides |
Project Management
Command | Purpose | Best For |
---|---|---|
estimate | Project estimation | Timeline planning, resource allocation |
task | Task management | Complex workflows, task tracking |
spawn | Meta-orchestration | Large-scale projects, parallel execution |
Utility Commands
Command | Purpose | Best For |
---|---|---|
git | Version control | Commit management, branch strategies |
index | Command discovery | Exploring capabilities, finding commands |
Session Commands
Command | Purpose | Best For |
---|---|---|
load | Context loading | Session initialization, project onboarding |
save | Session persistence | Checkpointing, context preservation |
reflect | Task validation | Progress assessment, completion validation |
select-tool | Tool optimization | Performance optimization, tool selection |