Command Code

Skills Quickstart

Get started with Agent Skills in Command Code. Let's create your first user-level and project-level skill.

User-level skill

Create a global code review skill

mkdir -p ~/.commandcode/skills/code-review cat > ~/.commandcode/skills/code-review/SKILL.md << 'EOF' --- name: code-review description: Perform thorough code reviews checking for bugs, security issues, and best practices --- # Code Review Checklist When reviewing code, check: ## Security - [ ] No hardcoded credentials or API keys - [ ] Input validation on all user data - [ ] Proper authentication and authorization ## Code Quality - [ ] Clear, descriptive variable names - [ ] Functions do one thing well - [ ] No code duplication - [ ] Edge cases handled ## Performance - [ ] No unnecessary loops or operations - [ ] Efficient data structures - [ ] Database queries optimized ## Testing - [ ] Unit tests cover main functionality - [ ] Edge cases tested - [ ] Error conditions tested EOF

Project-level skill

Create a project-specific API skill

mkdir -p .commandcode/skills/api-guidelines cat > .commandcode/skills/api-guidelines/SKILL.md << 'EOF' --- name: api-guidelines description: API design patterns and conventions for this project --- # API Guidelines ## Endpoint naming - Use plural nouns: `/users`, `/posts` - Use kebab-case: `/user-profiles` - Version in URL: `/v1/users` ## Response format \```json { "data": { ... }, "meta": { "count": 10, "page": 1 } } \``` ## Error handling - 400: Bad request (validation errors) - 401: Unauthorized - 403: Forbidden - 404: Not found - 500: Server error EOF

Using .agents/skills/ instead

If you already have skills in .agents/skills/, Command Code picks them up automatically. No migration needed.

.commandcode/skills/ takes priority on name conflicts. Skills from .agents/ show a [.agents] badge in the /skills UI.

Next steps