Enforce codebase quality through automated linting, auto-fixing, and multi-tiered reviews for security vulnerabilities (OWASP Top 10), performance issues, SOLID principles, and clean code patterns. Deeply analyze architecture, debug root causes from stack traces and logs, validate Markdown docs and Python projects, and run pre-commit hooks across JavaScript, Rust, Go, and more.
npx claudepluginhub melodic-software/claude-code-plugins --plugin code-qualityPROACTIVELY use for code quality analysis before commits or PRs. Reviews for bugs, security, performance, style violations, and CLAUDE.md compliance. Read-only plan mode with structured severity-rated findings. Uses code-reviewing skill for tiered checklist analysis.
Deep codebase analysis for patterns, architecture, and implementation details. PROACTIVELY use when understanding code structure, finding patterns across multiple files, analyzing dependencies, or answering architectural questions. More thorough than built-in Explore.
Root cause analysis and error investigation. PROACTIVELY use when encountering errors, exceptions, stack traces, failed tests, or unexpected behavior. Analyzes error messages, logs, and code flow to find and fix issues.
Quality-focused code reviewer for consensus mode. Reviews for SOLID principles, clean code patterns, performance issues, resource management, and code smells. Used alongside code-reviewer and security-reviewer for multi-agent consensus validation.
Security-focused code reviewer for consensus mode. Reviews for OWASP vulnerabilities, secrets exposure, authentication flaws, injection attacks, and cryptographic issues. Used alongside code-reviewer and quality-reviewer for multi-agent consensus validation.
Deep codebase analysis using codebase-analyst agent for patterns, architecture, and implementation details
Run markdown linting validation on files using markdownlint-cli2
Comprehensive markdown linting guidance using markdownlint-cli2. Run, execute, check, and validate markdown files. Fix linting errors (MD0XX rules). Configure .markdownlint-cli2.jsonc (rules and ignores). Set up VS Code extension and GitHub Actions workflows. Supports markdown flavors including GitHub Flavored Markdown (GFM) and CommonMark. Use when working with markdown files, encountering validation errors, configuring markdownlint, setting up linting workflows, troubleshooting linting issues, establishing markdown quality standards, or configuring flavor-specific rules for tables, task lists, and strikethrough.
Adaptive Python development guide with tiered complexity levels (Minimal/Standard/Full). Automatically selects appropriate guidance based on project context - from simple scripts (just clean Python code) to full production systems (complete tooling ecosystem). Covers modern conventions, testing, tooling, security, and best practices. Use when writing Python code, converting scripts, setting up projects, or building production systems. Keywords: PEP-8, Ruff, pytest, mypy, simple scripts, project structure, PyPI, packaging, type hints, clean code
Run comprehensive code review before commits, PRs, or releases. Uses code-reviewer agent with tiered security, performance, and quality checks.
Modifies files
Hook triggers on file write and edit operations
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimMarkdown documentation skills and linting with markdownlint.
This skill should be used when the model needs to ensure code quality through comprehensive linting and formatting. It provides automatic linting workflows for orchestrators (format → lint → resolve via concurrent agents) and sub-agents (lint touched files before task completion). Prevents claiming "production ready" code without verification. Includes linting rules knowledge base for ruff, mypy, and bandit, plus the linting-root-cause-resolver agent for systematic issue resolution.
Code review, refactoring, linting, anti-pattern detection, and static analysis
Automated code review, security scanning, and quality enforcement
Code quality enforcement, architecture skills, structural code graph, and impact-aware reviews.
Expert code review specialist. Proactively reviews code for quality, security, and maintainability. Use immediately after writing or modifying code.
Plugins for Claude Code: documentation management, code quality, and ecosystem support.
fnm (Fast Node Manager) is the recommended Node.js version manager for this project. It:
Install fnm:
# Windows (PowerShell as Admin)
winget install Schniz.fnm
# macOS/Linux
curl -fsSL https://fnm.vercel.app/install | bash
Configure for Git Bash (add to ~/.bashrc):
eval "$(fnm env --use-on-cd --shell bash)"
Or source the setup script which includes fnm initialization:
source "/path/to/claude-code-plugins/setup/bashrc-claude.sh"
Install Node:
fnm install 24
fnm default 24
npm install
npm run lint:md # Check for errors
npm run lint:md:fix # Auto-fix errors
Markdown linting runs automatically on PRs via GitHub Actions. The same rules apply locally and in CI.
/plugin install claude-ecosystem@claude-code-plugins
/plugin install code-quality@claude-code-plugins
/plugin install google-ecosystem@claude-code-plugins
This repo expects Codex CLI configuration to live in user scope under ~/.codex.
See .codex/README.md for the canonical locations.
| Plugin | Purpose |
|---|---|
| atlassian | Atlassian MCP server: Jira, Confluence, Compass integration |
| browser-automation | Browser automation MCP servers: Chrome DevTools, Playwright |
| business-analysis | BABOK techniques: capability mapping, stakeholder analysis, value streams, journey mapping |
| ci-cd | CI/CD pipelines: GitHub Actions, deployment automation, release management |
| claude-code-observability | Event logging, metrics, session diagnostics |
| claude-ecosystem | Claude Code docs, meta-skills, hooks, observability, auditors |
| code-quality | Code review, markdown linting, debugging, CI/CD templates |
| compliance-planning | Regulatory compliance: GDPR, HIPAA, PCI-DSS, AI governance, ISO 27001 |
| content-management-system | Headless CMS architecture: content modeling, taxonomies, media, theming |
| cursor-ecosystem | Cursor IDE docs, CLI, agent, keyword-based search |
| documentation-standards | Technical docs: arc42, C4 model, ADRs, RFC process, docs-as-code |
| dotnet | .NET 10+ automation: build, clean, SDK/tool install, version upgrades, Aspire MCP |
| duende-ecosystem | Duende IdentityServer, BFF, IdentityModel docs |
| enterprise-architecture | TOGAF, Zachman, ADRs, cloud alignment |
| event-modeling | Event-driven design: Event Modeling, Event Storming, CQRS, sagas |
| figma | Figma MCP server: design context, code generation, design tokens |
| formal-specification | Formal methods: UML/SysML, TLA+, OpenAPI/AsyncAPI, state machines |
| git | Git config, GPG signing, hooks, GitHub issues, history exploration |
| google-ecosystem | Gemini CLI docs, Claude-to-Gemini integration, configuration management |
| melodic-software | Developer onboarding, environment setup, commit workflows |
| microsoft | Microsoft MCP servers: Microsoft Learn, Azure, NuGet, Azure DevOps |
| milan-jovanovic | Milan Jovanovic .NET patterns: Clean Architecture, DDD, CQRS, EF Core |
| openai-ecosystem | OpenAI Codex CLI docs |
| requirements-elicitation | Requirements gathering: LLMREI interviews, gap analysis, prioritization |
| research | Research workflows: MCP integration, multi-source synthesis, structured output |
| response-quality | Response quality standards, source citations |
| security | Security: OWASP, authentication, cryptography, DevSecOps, threat modeling, 12 skills |
| soft-skills | Career progression, interviews, communication, professional visibility |