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
| Skill | What it does |
|---|---|
/commit | Generates a semantic commit message from git diff |
/diff | AI-powered review of uncommitted changes |
/review | Full code review with quality scoring |
/explain | Explains selected code in plain language |
/test | Generates unit tests for a file or function |
/fix | Fixes errors from the last command output |
/refactor | Suggests refactoring for cleaner code |
/docs | Generates JSDoc/docstring comments |
/security | Security audit of the current file |
/optimize | Performance optimization suggestions |
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_skilltool. 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.