Claude Code Extensions
A personal plugin marketplace for Claude Code. Drop-in extensions for the dev-workflow every project ends up reinventing.
Inspired by deepanscode/claude-code-extensions. Go take a look; it's worth the read.
Quick install
Copy-paste this to go from zero to working. Inside Claude Code:
/plugin marketplace add dilee/claude-extensions
/plugin install dev-workflow@dilee
/plugin install git-platform@dilee
Then in a terminal, finish git-platform setup (skip if you didn't install it):
# Find the plugin's install directory and run its setup script
find ~/.claude -type d -name git-platform -path '*/plugins/*' \
-exec sh -c 'cd "$1" && ./bin/setup.sh' _ {} \;
# Authenticate for the platforms you use (any subset)
gh auth login # GitHub
glab auth login # GitLab
export BITBUCKET_USERNAME="[email protected]" # Bitbucket
export BITBUCKET_TOKEN="your-api-token"
Restart Claude Code. Then verify inside any git repo:
"Detect the git platform for this repo."
If Claude reports your platform + owner + repo, you're done. Full walkthrough in plugins/git-platform/README.md.
Contents
Plugins
| Plugin | Version | What it is | Setup effort |
|---|
dev-workflow | 0.1.0 | Skills + agent — branch naming, ticket-driven branch creation, pre-PR docs-sync | None beyond /plugin install |
git-platform | 0.1.0 | MCP server — unified PR operations across GitHub / GitLab / Bitbucket | npm install + auth per platform |
Getting started
1. Add the marketplace (one time)
Inside Claude Code:
/plugin marketplace add dilee/claude-extensions
2. Install the plugins you want
/plugin install dev-workflow@dilee
/plugin install git-platform@dilee
Both are independent — install one or both.
3. Do per-plugin setup
Each plugin's README walks you through setup and usage. At minimum:
4. Keep the marketplace up to date
/plugin marketplace update
Quick reference per plugin
dev-workflow
Skills
| Skill | Type | Fires when |
|---|
branch-naming | auto-invoked | You're about to create or push a new branch — enforces feature/, bugfix/, hotfix/, release/ prefixes. |
ticket-start | user-invoked | You type /ticket-start <KEY> or ask Claude to start a ticket — fetches the ticket, proposes the correct branch, creates it on confirmation. |
Agents
| Agent | What it does |
|---|
docs-sync | Scans the current branch vs base and lists doc gaps before you open the PR. Reports only; doesn't edit. |
Full docs: plugins/dev-workflow/README.md.
git-platform
Nine MCP tools, unified across GitHub / GitLab / Bitbucket, platform auto-detected from the git remote:
| Tool | What it does |
|---|
git_platform_detect | Detect platform + owner/repo. |
repo_info | Default branch, visibility, description, URL. |
pr_create / pr_list / pr_view | Create / list / view PRs. |
pr_merge / pr_approve / pr_comment / pr_decline | Act on PRs. |
Example prompts Claude maps to these tools:
- "Open a draft PR from
feature/PROJ-123 into main."
- "List my open PRs."
- "Show me PR 42 with the diff and CI status."
- "Squash-merge PR 42 and delete the branch."
Full docs (install, auth, self-hosted, troubleshooting): plugins/git-platform/README.md.
Project-parameters contract
dev-workflow adapts to each project by reading its CLAUDE.md (or AGENTS.md). Drop this block into yours:
## Project conventions (read by Claude Code extensions)
- Ticket key format: `[A-Z]+-\d+` # adjust to your tracker, e.g. `PROJ-\d+`
- Integration branch: `main` # or `develop` if you use Git Flow
- Tracker: Jira # Jira | Linear | GitHub | GitLab
- Docs folder: `docs/`
- ADR folder: `docs/adr/`
