A Claude Code plugin repository.
This repository contains multiple Claude Code plugins organized in a monorepo structure:
claude/
├── plugins/
│ ├── standard/ # Standard plugin with quality tools
│ │ ├── commands/git/
│ │ │ └── commit.md # /git:commit slash command
│ │ ├── agents/
│ │ │ ├── quality-orchestrator.md # Coordinates quality workflows
│ │ │ ├── claude-code-quality-runner.md # Reviews config files
│ │ │ └── claude-code-quality-resolver.md # Fixes config issues
│ │ ├── skills/ # Agent Skills with SKILL.md files
│ │ ├── hooks/ # Event handlers (hooks.json)
│ │ └── .mcp.json # MCP servers for standard plugin
│ └── ruby/ # Ruby plugin with RuboCop tools
│ ├── agents/
│ │ ├── rubocop-runner.md # Analyzes Ruby code with RuboCop
│ │ └── rubocop-resolver.md # Fixes RuboCop violations
│ └── skills/ # Ruby-specific agent skills
Place markdown files in the plugins/standard/commands/ directory to create custom slash commands. Each file becomes a command that Claude can execute.
A slash command /git:commit that creates git commits following best practices:
- Quality Checks: Automatically invokes the quality-orchestrator before committing
- Commit Message Conventions: Follows repository style and includes Claude Code attribution
- Safety: Warns about sensitive files, validates changes, prevents empty commits
- Scoped Permissions: Only allows specific git commands (status, diff, log, add, commit, show)
The command MUST run quality checks before every commit to ensure code quality and compliance.
This plugin includes specialized subagents in the plugins/standard/agents/ directory:
A generic quality orchestration agent that:
- Discovers runner/resolver pairs dynamically across all working directories
- Coordinates quality review workflows before commits
- Pairs runners (that find issues) with resolvers (that fix them) by matching names and file patterns
- Works across different project structures without hardcoded paths
Unlike directory-specific orchestrators, this agent searches for quality agents by pattern:
- Runners:
*-runner.mdor*runner*.md - Resolvers:
*-resolver.mdor*resolver*.md
Use it proactively before commits to ensure code quality through automated review and fix workflows.
Reviews Claude Code configuration files for security, compliance, and best practices:
- Security Review: Checks
.claude/settings.jsonfor dangerous permissions and overly broad tool access - RFC 2119 Compliance: Ensures proper use of requirement keywords (MUST, SHOULD, MAY) in configuration files
- Minimum Permissions: Verifies commands, agents, and skills use only necessary tools
Automatically invoked by the quality-orchestrator for .claude/ configuration files. Produces structured reports without making modifications.
Automatically fixes issues identified by the quality-runner:
- Security Fixes: Restricts overly permissive tool access in settings
- RFC 2119 Compliance Fixes: Updates informal language to proper RFC 2119 keywords
- Permission Scoping Fixes: Reduces tool access to minimum necessary permissions
Paired with the quality-runner by the orchestrator. Applies fixes automatically and reports results.
Create agent Skills in the plugins/*/skills/ directory. Each skill SHOULD have a SKILL.md file that extends Claude's capabilities.
Configure event handlers in plugins/*/hooks/hooks.json to respond to Claude Code events like tool calls or user interactions.
Each plugin can configure its own MCP (Model Context Protocol) servers. The standard plugin includes MCP servers in plugins/standard/.mcp.json:
- filesystem: File system operations with read/write access
- git: Git repository operations and version control
- sequential-thinking: Enhanced reasoning and step-by-step problem solving
- time: Current time and date information
These servers activate automatically when the standard plugin is enabled. Plugins that do not require MCP servers MAY include an empty .mcp.json file with {"mcpServers": {}} to maintain consistent structure.
To use this plugin with Claude Code:
- Copy or clone this repository to your plugins directory
- Configure via a marketplace manifest, or
- Install directly using the Claude Code CLI
Each plugin can have its own configuration:
- Standard Plugin: General-purpose quality tools, git commands, and MCP servers
- Ruby Plugin: RuboCop integration for Ruby code analysis and fixing
Plugin metadata and configuration can be customized per plugin.
The configured MCP servers require no additional environment variables. All servers will work out of the box when their respective plugins are enabled.