Skills
Skills are pre-built prompt shortcuts that expand into full instructions before being sent to the AI. They save time on common, repetitive tasks.
/skills inside Codeep to see all available skills.Built-in skills
All 47 built-in skills, generated from the CLI. Shortcuts are in brackets — /t runs /test.
| Skill | What it does |
|---|---|
/commit (/c) | Generate commit message and commit changes |
/amend | Amend the last commit |
/push (/p) | Push changes to remote |
/pull | Pull latest changes from remote |
/pr | Create a pull request description |
/changelog | Generate changelog from recent commits |
/branch | Create a new branch with smart naming |
/stash | Stash changes with a meaningful message |
/unstash | Apply and drop the most recent stash |
/test (/t) | Generate tests for current file or function |
/test-fix | Fix failing tests |
/coverage | Analyze test coverage and suggest improvements |
/e2e | Generate end-to-end tests |
/mock | Generate mock data for testing |
/readme | Generate or update README |
/explain (/e) | Explain how the code works |
/api-docs | Generate API documentation |
/translate | Translate code comments to English |
/refactor (/r) | Refactor code for better quality |
/types | Add or improve TypeScript types |
/optimize (/o) | Optimize code performance |
/cleanup | Clean up code (remove unused, format) |
/modernize | Update code to use modern syntax |
/migrate | Migrate code to newer version |
/split | Split a large file into smaller modules |
/debug (/b) | Debug and fix issues |
/fix (/f) | Fix a specific error or issue |
/security | Security audit |
/log | Add logging to code |
/build | Build the project |
/deploy | Build and deploy |
/release | Create a new release |
/publish | Publish package to npm |
/component | Generate a React/Vue component |
/api | Generate an API endpoint |
/hook | Generate a React hook |
/service | Generate a service/utility module |
/page | Generate a new page/route |
/form | Generate a form with validation |
/crud | Generate full CRUD for an entity |
/docker | Generate Dockerfile and docker-compose |
/ci | Generate CI/CD configuration |
/env | Setup environment configuration |
/k8s | Generate Kubernetes manifests |
/terraform | Generate Terraform configuration |
/nginx | Generate Nginx configuration |
/monitor | Add monitoring and observability |
Custom skills
You can define your own skills in .codeep/skills/. Each skill is a .md file with the skill name as filename and the prompt as content.
Skill bundles (new in 2.0)
Beyond the built-in shortcuts above, Codeep 2.0 introduces structured skill bundles — directory-based capability packs the agent discovers and invokes on its own. Different concept from the slash-command shortcuts: bundles are picked by the model when the user's intent matches.
Format
A bundle is a directory containing a SKILL.md file:
.codeep/skills/deploy-staging/SKILL.md # project-scoped (commit with repo)
~/.codeep/skills/deploy-staging/SKILL.md # global (this machine, all projects)SKILL.md is Markdown with a YAML frontmatter header. The format is a superset of Claude Code skills — paste an existing one and it just works.
---
name: deploy-staging
description: Deploy the current branch to staging via npm scripts.
triggers: [deploy, ship, release]
# Optional Codeep-specific extensions:
codeep-min-version: 2.0.0
codeep-requires-mcp: [postgres]
allowed-tools: [read_file, write_file, execute_command]
version: 0.1.0
---
# deploy-staging
Run the test suite, build, then `npm run deploy:staging`. If the
build fails, surface the error and stop — don't deploy a broken build.How the agent invokes them
Each agent iteration ships the bundle catalog inside the system prompt, plus an invoke_skill tool. When the user's request pattern-matches a skill's name / description / triggers, the model calls invoke_skill with the skill name; Codeep returns the SKILL.md body and the agent follows the steps.
Managing bundles
| Command | What it does |
|---|---|
/skills bundles | List installed bundles (project + global) |
/skills create-bundle <name> | Scaffold a new project bundle in .codeep/skills/ |
/skills show <name> | Print the SKILL.md for a bundle |
/skills browse [query] | Search the public marketplace at codeep.dev |
/skills install <owner>/<slug> | Pull a marketplace bundle into the project |
/skills publish <slug> [--public] | Share your bundle to codeep.dev |
/skills unpublish <owner>/<slug> | Remove your published bundle |
From the VS Code extension the same operations live in the command palette as Codeep: Browse Skill Bundles…, Codeep: Create Skill Bundle…, and Codeep: Open Skills Folder.
Marketplace (codeep.dev/skills)
Public skills are browseable at codeep.dev/skills. Sign in to manage your own at /dashboard/skills — toggle visibility, unpublish, see install counts.
execute_command. Before invoking an unfamiliar skill — especially one installed from the public marketplace — open the SKILL.md and any scripts/ files to confirm what it does. Codeep flags project-scoped bundles in the welcome banner so you know what's loaded.