Full-featured development toolkit with code review, linting, security scanning, and database tools.
Writes and improves documentation — READMEs, API docs, inline comments, and guides. Use when the user wants to document code, write a README, or improve existing docs.
Reviews code for security vulnerabilities — injection, auth flaws, data exposure, and dependency risks. Use when auditing code for security, reviewing PRs for security concerns, or checking for OWASP Top 10 issues.
Reviews code for bugs, style issues, and improvements. Use when the user asks to review code, check a PR, or audit code quality.
Explains error messages and stack traces. Use when the user shares an error, exception, or crash log and wants to understand what went wrong.
Explains error messages and stack traces. Use when the user shares an error, exception, or crash log and wants to understand what went wrong.
Modifies files
Hook triggers on file write and edit operations
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A full-featured development toolkit plugin demonstrating every Open Plugin component type.
| Component | Files | What it does |
|---|---|---|
| Skills | skills/code-review/, skills/explain-error/ | Code review checklist and error explainer |
| Commands | commands/status.md, commands/deploy.md | Project health dashboard and deployment |
| Agents | agents/security-reviewer.md, agents/docs-writer.md | Security audit and documentation writing |
| Rules | rules/prefer-const.mdc, rules/error-handling.mdc | Coding standards enforced automatically |
| Hooks | hooks/hooks.json | Auto-lint on file edits, env check on session start |
| MCP Server | .mcp.json | Postgres database access via MCP |
| LSP Server | .lsp.json | TypeScript language server for code intelligence |
devtools/
├── .plugin/
│ └── plugin.json
├── skills/
│ ├── code-review/
│ │ ├── SKILL.md
│ │ └── scripts/review-helper.sh
│ └── explain-error/
│ └── SKILL.md
├── commands/
│ ├── status.md
│ └── deploy.md
├── agents/
│ ├── security-reviewer.md
│ └── docs-writer.md
├── rules/
│ ├── prefer-const.mdc
│ └── error-handling.mdc
├── hooks/
│ └── hooks.json
├── scripts/
│ ├── auto-lint.sh
│ └── check-env.sh
├── .mcp.json
├── .lsp.json
└── assets/
└── logo.svg
claude --plugin-dir ./examples/full-plugin
Then try:
/devtools:status — project health check/devtools:deploy staging — deploy to stagingcode-review and explain-error skills activate automatically based on task contextsecurity-reviewer and docs-writer agents are available via /agentsSome components require external tools:
POSTGRES_URL environment variabletypescript-language-server (npm install -g typescript-language-server typescript)eslint and/or ruff for auto-linting (optional — hooks degrade gracefully)npx claudepluginhub uncurated-tests/sample-plugin --plugin devtoolsComprehensive development toolkit: 52 professional skills covering code quality, testing, API development, security, databases, DevOps, and more
Complete plugin development toolkit for creating, refactoring, and validating Claude Code plugins and agents. Use when creating new plugins/skills/agents, refactoring existing plugins/skills, validating frontmatter, or restructuring plugin components. Includes specialized agents for assessment, planning, execution, and validation workflows.
Agents for code review, security audits, debugging, and quality assurance
Diagnose and fix Claude Code configuration issues including plugin registry, settings, hooks, and MCP servers
Specialized security review subagent
Complete developer toolkit for Claude Code