Skip to main content

​
Custom Commands

The Custom Commands feature allows you to encapsulate frequently used prompts and workflows into reusable commands. Simply type / in the Agent dialog to quickly invoke these commands, significantly improving your daily development efficiency. Whether you frequently perform code reviews, generate test cases, or need quick access to project specifications, custom commands can simplify repetitive operations into “one-click” tasks.

​
Command Types and Scope

FeatureUser CommandsProject Commands
ScopeApplies to all projects for the current userOnly effective in the current project root directory and its subdirectories
Storage Path- macOS / Linux: /home/<username>/.qoder/commands/ or /Users/<username>/.qoder/commands/
- Windows: C:\Users\<username>\.qoder\commands\		<project-root>/.qoder/commands/
Use CasesGeneral development tasks, such as:
• Code review
• Generate unit tests		Project-specific tasks, such as:
• Check project API specifications
• Validate configuration file format
SharingLimited to current user onlyCan be shared with team members via Git or other version control systems
Note: User-level commands do not support cross-device synchronization. You can manually migrate configuration files.

​
Creating Custom Commands

  1. Open the Command Management Interface
    • Method 1: Go to the Commands page in Qoder Settings and click the “Add” button
    • Method 2: Type / in the dialog and click the “Add Command” shortcut at the bottom
  2. Enter a unique command name (e.g., gen-test) in the top search bar, then press Enter.
  3. Select the command type:
    • User-level: Universal commands applicable to all projects
    • Project-level: Only available in the current project
  4. Fill in the complete prompt content in the guidance area. Your command will be automatically saved after saving the file.
  5. Return to the conversation and type / in the dialog to see your newly created command.

​
Example Commands

## Overview
Systematic framework for evaluating source code to verify technical excellence, robustness, and security compliance.

## Evaluation Areas

### Technical Implementation
- [ ] Requirements accurately implemented
- [ ] Algorithm efficiency validated
- [ ] Resource management optimized
- [ ] Performance considerations addressed
- [ ] System integration verified

### Development Standards
- [ ] Design patterns properly applied
- [ ] Code modularity maintained
- [ ] Documentation completeness
- [ ] Test coverage adequate
- [ ] Logging implementation
- [ ] Error handling strategy

### Risk Management
- [ ] Security best practices followed
- [ ] Data validation comprehensive
- [ ] Authentication methods secure
- [ ] Authorization rules defined
- [ ] API security verified

### Maintenance Aspects
- [ ] Code maintainability
- [ ] Dependency management
- [ ] Version compatibility
- [ ] Technical debt assessment
→ Try in Qoder
## Overview
Systematic examination of system security posture focusing on vulnerability detection, threat prevention, and compliance validation.

## Assessment Areas
1. **Application Security**
   - Source code vulnerability scan
   - Security patch status
   - Framework security audit
   - Library version control

2. **Authentication System**
   - Identity management review
   - Password policy compliance
   - Multi-factor authentication
   - Session management audit

3. **Data Protection**
   - Encryption implementation
   - Data access patterns
   - Privacy compliance
   - Backup security

4. **System Architecture**
   - Network segmentation
   - Firewall configuration
   - Load balancer security
   - API gateway protection

## Verification Points
### Core Requirements
- [ ] Security patches applied
- [ ] Encryption standards met
- [ ] Access controls verified
- [ ] Audit logs enabled
- [ ] Intrusion detection active

### Advanced Measures
- [ ] Penetration test completed
- [ ] Security monitoring configured
- [ ] Disaster recovery tested
- [ ] Incident response plan updated
→ Try in Qoder
## Overview
Standardized process for submitting code changes with comprehensive documentation and validation requirements.

## Preparation Steps
1. **Code Quality Assurance**
   - Static code analysis completed
   - Code formatting verified
   - Unused code removed
   - Comments updated
   - Test coverage confirmed

2. **Change Documentation**
   - Implementation details
   - Technical decisions
   - Performance impact
   - Migration steps
   - Rollback procedure

3. **Testing Verification**
   - Unit tests executed
   - Integration tests passed
   - Performance tests run
   - UI/UX validation done
   - Cross-browser testing

## Submission Requirements
### Documentation
- [ ] Architecture changes noted
- [ ] API modifications documented
- [ ] Configuration updates listed
- [ ] Dependencies documented

### Quality Gates
- [ ] Code review approved
- [ ] Security review passed
- [ ] Performance criteria met
- [ ] CI/CD pipeline green

### Post-Merge Plan
- [ ] Deployment strategy
- [ ] Monitoring setup
- [ ] Feature flags configured
- [ ] Backup procedure
→ Try in Qoder
## Overview
Execute project test suite and resolve detected issues through systematic troubleshooting and verification.

## Testing Phases
1. **Environment Setup**
   - Verify development environment
   - Check dependencies status
   - Confirm test data availability
   - Validate configuration settings

2. **Test Execution**
   - Run unit test suite
   - Execute integration tests
   - Perform smoke tests
   - Check code coverage

3. **Issue Resolution**
   - Document test failures
   - Analyze error patterns
   - Debug failed cases
   - Implement fixes

## Validation Matrix
### Core Tests
- [ ] Unit test completion
- [ ] API test verification
- [ ] Database test results
- [ ] Cache behavior check

### System Health
- [ ] Memory usage normal
- [ ] Response times acceptable
- [ ] Error rates within limits
- [ ] Resource utilization stable

## Resolution Flow
1. **Fix Implementation**
   - Address critical issues first
   - Apply necessary patches
   - Update test cases
   - Document changes
→ Try in Qoder
## Overview
Create and save a structured markdown file (agents.md) that defines AI agent specifications for model comprehension.

## Generation Workflow
1. **File Creation**
   - Set file path: ./docs/agents.md
   - Create directory if not exists
   - Initialize markdown file
   - Set file permissions

2. **Content Generation**
   - Write file header
   - Generate metadata section
   - Create main content blocks
   - Add version control info

3. **Document Structure**
   - Define agent identity
   - List capabilities and limits
   - Specify interaction rules
   - Document dependencies

## File Components
### Required Sections
- [ ] File metadata
- [ ] Agent definition
- [ ] Capability matrix
- [ ] Interaction protocols
- [ ] Version information

### File Operations
- [ ] Directory check
- [ ] File creation
- [ ] Content writing
- [ ] Permission setting

## Validation Steps
1. **File Verification**
   - Check file existence
   - Validate markdown syntax
   - Verify content structure
   - Confirm file accessibility
→ Try in Qoder