A Claude Code plugin marketplace for ITK Dev team tools and MCP servers.
itkdev-claude-plugins/
├── .claude-plugin/
│ ├── plugin.json # Plugin manifest
│ ├── marketplace.json # Marketplace catalog
│ └── mcp-versions.json # Tracked MCP dependency versions
├── .github/workflows/ # GitHub Actions workflows
│ ├── check-mcp-updates.yml # Weekly MCP update checker
│ └── release.yml # Automated release workflow
├── .mcp.json # MCP server configurations
├── commands/ # Slash commands (Markdown files)
│ └── example.md
├── skills/ # Skills (Markdown files with frontmatter)
│ └── itkdev-github-guidelines.md
└── README.md
Team members can install the marketplace and plugins with:
# Add the marketplace
/plugin marketplace add itk-dev/itkdev-claude-plugins
# Install the itkdev-tools plugin
/plugin install itkdev-tools@itkdev-marketplaceBrowser feedback collection tool from mcp-claude-code-browser-feedback.
GitHub workflow guidelines for the ITK Dev team. Automatically activates when working with Git, branches, commits, or pull requests. Covers:
- Branch naming conventions (
feature/issue-{number}-{description}) - Conventional commit messages
- Changelog updates (Keep a Changelog format)
- PR requirements and templates
This plugin automatically releases new versions when MCP server dependencies publish updates.
- Daily Check: A GitHub Actions workflow runs every day at 8:30 UTC
- Version Comparison: Compares latest MCP releases with tracked versions in
.claude-plugin/mcp-versions.json - Automated Release: If updates are detected, a new patch version is released automatically
| MCP Server | Repository |
|---|---|
| browser-feedback | mcp-claude-code-browser-feedback |
| docker | mcp-itkdev-docker |
You can manually trigger a dependency check via the GitHub Actions UI:
- Go to Actions > Check MCP Updates
- Click Run workflow
Edit .mcp.json to add new MCP server configurations:
{
"mcpServers": {
"your-server": {
"command": "npx",
"args": ["-y", "github:org/repo"]
}
}
}Create new Markdown files in the commands/ directory. Each file becomes a slash command.
Create new Markdown files in the skills/ directory with YAML frontmatter:
---
name: skill-name
description: When this skill should be activated automatically.
---
# Skill Content
Your skill instructions here...