code-quality
97Command
Part of core
Check code quality issues (long functions, complexity, violations).
511 tagged claude-code-plugins, measured the same way as everything else here.
Browse within: claude-code-marketplace 150agent-skill-repository 66agentic-skills 66claude-ai 42claude-cowork-plugin 41claude-code-hooks 38claude-code-skill 32claude-code-plugins-marketplace 31branding 25content-generation 25product-management 25jj 23jujutsu 23vcs 23
Command
Part of core
Check code quality issues (long functions, complexity, violations).
Command
Part of core
Check dependency versions across all project repositories.
Command
View your CodeSensei learning dashboard — belt rank, XP, streaks, and skills.
Command
Test your understanding with a quick quiz based on what you've been building.
Command
Get a summary of everything you learned this session — concepts, quizzes, and progress.
Command
Part of app-dev
Audit a Next.js project for common issues, anti-patterns, and misconfigurations.
Command
Part of app-dev
Audit authentication and authorization implementation for security issues.
Command
Part of app-dev
Find and clean up unused files, dependencies, exports, and types with knip.
Command
Part of patrol
List all Patrol commands, skills, and config options.
Command
Part of patrol
Manage custom trigger keywords — list, add, remove, or reset.
Command
Part of patrol
Show patrol dashboard — mode, tier, health, verification, config.
Jose-Ribeir/claude-code-review-gate
Command
Part of review-gate
Check that the review-gate push gate is actually wired up and able to run. Reports which adapters are active, whether the reviewer can be located, and any version skew between the plugin and the global git hook. Use when a push was not reviewed, when a gate error told you to run the doctor, or after installing or…
Command
Part of specweaver
Systematic bug investigation and fixing workflow for existing features. Uses code-reviewer for deep analysis, code-consolidator for context, parallel web research for solutions, and atomic phase implementation with review gates.
Command
Part of specweaver
Design and implement a new feature with parallel best-practice research, codebase exploration, architectural planning, atomic phase specs, phase-by-phase code review, and automated documentation.
Command
Part of specweaver
Refactor an existing feature with deep code understanding, documentation review, atomic phase breakdown, incremental changes, and comprehensive review loops.
keskinonur/claude-plugin-fizzy
Command
Part of fizzy
Configure which Fizzy.do board to sync todos to.
keskinonur/claude-plugin-fizzy
Command
Part of fizzy
Show Fizzy.do connection and sync status.
keskinonur/claude-plugin-fizzy
Command
Part of fizzy
Manually trigger todo sync to Fizzy.do.
lukaskellerstein/claude-my-marketplace
Command
Part of design-plugin
Create a design direction and styleguide for a project — produces aesthetic direction, fonts, colors, imagery, and media prompts.
lukaskellerstein/claude-my-marketplace
Command
Part of media-plugin
List, organize, and manage generated media assets in the output directory.
lukaskellerstein/claude-my-marketplace
Command
Part of media-plugin
Generate a media asset — image, video, music, or speech — with guided prompts and sensible defaults.
Command
Part of dev-workflows
BRD customer-package workflow (PM phase, fifth command of the BRD-to-PRD route). Gates on the BRD's decisions being merged and on every interview question carrying a terminal disposition or the held-for-the-customer holding state, then runs an adversarial self-review through brd-package-reviewer and refuses to build a…
Command
Part of dev-workflows
BRD reconciliation workflow (PM phase, sixth and last command of the BRD-to-PRD route). Takes the customer's returned review from anywhere, copies it into the BRD folder under the canonical name and commits it before anything reads it, then dispatches customer-review-reader in schema or free-text mode. Confirms every…
Command
Part of dev-workflows
Jira-driven feature-documentation workflow. Phase 0 preflight-discovers the docs repo + profile (in-repo → built-in example-docs default → on-demand /docs-profile) and the PRD's specs dir under /workspace. Reads a Product Requirements Document hierarchy from exported markdown, resolves PR diffs in parallel…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: