Plugin
code-review
Automated pull request review with /code-review: four parallel agents, confidence scoring and an 80 point threshold.
- Quality
Plugins listed in the directory, each with the command that installs it.
A plugin is what Claude Code installs. One plugin can hold slash commands, agents, skills, hooks, MCP servers and mods, so a single install adds all of them.
Read more in the Install plugins in the Claude Code docs (opens in a new tab).
Plugin
Automated pull request review with /code-review: four parallel agents, confidence scoring and an 80 point threshold.
Plugin
Slash commands for git workflows: /commit, /commit-push-pr and /clean_gone, published in the anthropics/claude-plugins-official repository.
Plugin
A guided 7-phase feature workflow behind /feature-dev, with code-explorer, code-architect and code-reviewer agents.
Plugin
Create Claude Code hooks from markdown rule files instead of editing hooks.json, or derive rules from your conversation.
Plugin
Toolkit for building Claude Code plugins: seven skills, three agents and an end-to-end /plugin-dev:create-plugin workflow.
Plugin
Six review agents for pull requests (comments, tests, error handling, types, code quality, simplification) and a /review-pr command.
Plugin
Three layers of security review for Claude-generated code: regex warnings on edits, an LLM diff review on Stop, and an agentic commit review.
Plugin
Generates an explorable HTML report of Claude Code usage from local session transcripts: tokens, cache, subagents, skills, costly prompts.
To search these or narrow them by category, open them in the directory.
You install a plugin from a marketplace with /plugin install and the plugin's name followed by @ and the marketplace's name. Claude Code adds Anthropic's official marketplace, claude-plugins-official, the first time you start an interactive terminal session; any other marketplace must be added first.
A plugin can run code on your machine with your user permissions, so install only plugins you trust.
Before you install anything, read what the directory checks and what it does not.
/plugin marketplace add <owner>/<repo>
/plugin install <plugin>@<marketplace>