set-current-spec
This skill should be used when switching between specs, after creating a new spec with "/spec-kit:specify", when the user says "switch to spec 002" or "work on feature X", or when resuming work on a different feature. Updates progress.yml with the current working specification.
SKILL.md
| Name | set-current-spec |
| Description | This skill should be used when switching between specs, after creating a new spec with "/spec-kit:specify", when the user says "switch to spec 002" or "work on feature X", or when resuming work on a different feature. Updates progress.yml with the current working specification. |
Retso Marketplace
Custom marketplace for Claude Code plugins.
About
This marketplace provides a curated collection of Claude Code extensions including plugins, commands, agents, hooks, and MCP servers.
Installation
Users can add this marketplace to their Claude Code installation using one of the following methods:
From GitHub
/plugin marketplace add retsohuang/retso-marketplace
From Local Path
/plugin marketplace add /path/to/retso-marketplace
From Git URL
/plugin marketplace add https://github.com/retsohuang/retso-marketplace.git
Using Plugins
Once the marketplace is added, install plugins with:
/plugin install plugin-name@retso-marketplace
List available plugins:
/plugin marketplace list
Testing Plugins Locally
Use the --plugin-dir flag to test any plugin during development without installing it:
claude --plugin-dir ./plugins/my-plugin
Once Claude Code starts, try your plugin's skills with /plugin-name:skill-name. You can load multiple plugins at once:
claude --plugin-dir ./plugins/plugin-one --plugin-dir ./plugins/plugin-two
Restart Claude Code to pick up changes as you iterate on your plugin.
Adding Plugins to This Marketplace
Local Plugins
-
Create your plugin directory under
plugins/:mkdir -p plugins/my-plugin -
Add your plugin files (commands, agents, hooks, etc.)
-
Update
.claude-plugin/marketplace.jsonto include your plugin:{ "name": "my-plugin", "description": "Description of my plugin", "version": "1.0.0", "source": "./plugins/my-plugin", "author": { "name": "Your Name", "email": "your.email@example.com" }, "license": "MIT", "keywords": ["keyword1", "keyword2"] }
External Plugins (GitHub)
Reference plugins from other repositories:
{
"name": "external-plugin",
"description": "Plugin from another repository",
"version": "1.0.0",
"source": {
"source": "github",
"repo": "organization/plugin-repository"
},
"license": "MIT"
}
External Plugins (Git URL)
Reference plugins from any Git server:
{
"name": "git-plugin",
"description": "Plugin from custom Git server",
"version": "1.0.0",
"source": {
"source": "url",
"url": "https://gitlab.com/team/plugin-repo.git"
},
"license": "MIT"
}
Plugin Structure
A typical plugin in this marketplace should follow this structure:
plugins/my-plugin/
├── .claude-plugin/
│ └── plugin.json # Plugin metadata
├── commands/ # Slash commands
│ └── my-command.md
├── agents/ # AI agents
│ └── my-agent.md
├── hooks/ # Event hooks
│ └── hooks.json
└── mcp-servers/ # MCP server configs
└── server-config.json
Marketplace Configuration
The marketplace is configured in .claude-plugin/marketplace.json. Key fields:
- name: Marketplace identifier (kebab-case)
- owner: Maintainer information
- description: Marketplace description
- version: Marketplace version
- pluginRoot: Base path for local plugins (default:
./plugins) - plugins: Array of plugin definitions
Available Plugins
| Plugin Name | Description | Version |
|---|---|---|
| code-review-tools | Review code changes commit-by-commit with custom rules support. Includes interactive setup and rule creation. | 2.1.1 |
| github-tools | GitHub workflow tools for daily development. Analyze PR review comments and categorize what needs fixing. | 0.1.1 |
| worktree-bootstrap | Automatically copy gitignored files to new worktrees using .worktreeinclude.yaml | 0.1.0 |
Contributing
To contribute a plugin to this marketplace:
- Fork this repository
- Add your plugin to the
plugins/directory or reference it externally - Update
.claude-plugin/marketplace.jsonwith your plugin entry - Update the Available Plugins table in this README
- Submit a pull request
License
Individual plugins may have their own licenses. Check each plugin's license field in the marketplace configuration.
Contact
Maintainer: Retso Huang (retsohuang@gmail.com)