Monitor code complexity and maintain code quality
You can install this plugin from any of these themed marketplaces. Choose one, add it as a marketplace, then install the plugin.
This plugin uses advanced features that require additional trust:
Only install plugins from repositories you trust. Review the source code before installation.
Choose your preferred installation method below
A marketplace is a collection of plugins. Every plugin gets an auto-generated marketplace JSON for individual installation, plus inclusion in category and themed collections. Add a marketplace once (step 1), then install any plugin from it (step 2).
One-time setup for access to all plugins
When to use: If you plan to install multiple plugins now or later
Step 1: Add the marketplace (one-time)
/plugin marketplace add https://claudepluginhub.com/marketplaces/all.jsonRun this once to access all plugins
Step 2: Install this plugin
/plugin install hook-complexity-monitor@allUse this plugin's auto-generated marketplace JSON for individual installation
When to use: If you only want to try this specific plugin
Step 1: Add this plugin's marketplace
/plugin marketplace add https://claudepluginhub.com/marketplaces/plugins/hook-complexity-monitor.jsonStep 2: Install the plugin
/plugin install hook-complexity-monitor@hook-complexity-monitorVersion: 2.0.4 | Last Updated: 2025-10-19
/speckit.* commands and INSTRUCTION parameters/spec-kit:specify to prompt for committing existing changes/speckit.specify now asks about branch publishing (publish/local commit/decide later)CURRENT_BRANCH declarations across all command files/spec-kit:* and /speckit.*.specify/memory/ to specs/[branch-name]/ structure for feature files/spec-kit:specify command now offers choice between creating new specs or rewriting existing onescreate-new-feature.ps1 script for automated branch creation/spec-kit:init now detects existing installations and asks user confirmation before re-initializing$ARGUMENTS for user input/spec-kit:specify Add user authentication)/spec-kit:plan, /spec-kit:tasks, and /spec-kit:implement commands.specify/temp//pair, /review, /suggest, /fix, /explain@code-reviewer, @bug-hunter, @architect, @performance-expertoutputFormats configuration.complexity-log.md to .{project-name}-complexity-log.md (same for all hooks).state directory.plugin-config/ filesshowLogs settingincludeEmptyDirs configuration option to control empty directory inclusionincludeExtensions and excludeExtensions configuration options.js, .ts, .json).meta, .log, .tmp).meta or meta).{project-name}-project-structure.md)includeDirs configuration to scan only specific directoriesincludeDirs takes precedence over excludeDirs when setunity-uitoolkit skill for UI Toolkit development assistance@unity-refactor agent for code refactoring and quality improvement/unity:new-script, /unity:optimize-scene, /unity:setup-test@unity-scripter, @unity-performance, @unity-architect (expanded to 4 in v1.1.0)unity-script-validator, unity-scene-optimizer, unity-template-generator, unity-ui-selector (expanded to 5 in v1.2.0)⚠️ Important Notice (v2.0.17) There is a known issue where hook logs stack in the chat window. Until this is resolved, PostToolUse hook outputs are hidden using
suppressOutput: truein hooks.json. Stop hook messages can be controlled via.plugin-config/[plugin-name].jsonwith"showLogs": false(default). Set totrueto enable. See Configuration for details.
A collection of powerful productivity plugins for Claude Code to automate common development workflows.
Automatically creates git commits after each Claude Code session to prevent work loss.
Quick Info: Auto-commits all changes with timestamps when session ends | Hook: Stop
Scans your entire project and collects all TODO, FIXME, HACK, XXX, NOTE, and BUG comments into a detailed report.
Quick Info: Supports multiple languages, generates markdown report | Hooks: PostToolUse (Write|Edit|NotebookEdit), Stop
Monitors code complexity metrics and warns when thresholds are exceeded.
Quick Info: Tracks cyclomatic complexity, function/file length, nesting depth | Hook: PostToolUse (Edit|Write)
Automatically scans and documents your project structure with directory tree, scripts, and dependencies.
Quick Info: Generates project structure documentation, tracks file changes, extracts package.json info | Hooks: PostToolUse (Write), Stop
Tracks all file operations during a session and generates a summary report with directory tree visualization.
Quick Info: Classifies files by operation type (Created, Modified, Read) | Hooks: PostToolUse (Write|Edit|Read|NotebookEdit), Stop
Complete AI pair programming experience with slash commands, expert agents, and intelligent hooks integrated together.
Quick Info: 5 slash commands + 4 expert agents + 3 intelligent hooks | Commands: /pair, /review, /suggest, /fix, /explain | Agents: @code-reviewer, @bug-hunter, @architect, @performance-expert
GitHub Spec-Kit integration for Specification-Driven Development (SDD). Define WHAT and HOW before coding.
Quick Info: 10 slash commands for structured development workflow | Commands: /spec-kit:init, /spec-kit:constitution, /spec-kit:specify, /spec-kit:plan, /spec-kit:tasks, /spec-kit:implement | Workflow: Constitution → Specification → Plan → Tasks → Implementation
Comprehensive Unity game development toolkit with intelligent scripting assistance, code refactoring, performance optimization, and UI Toolkit support.
Quick Info: 4 expert agents + 5 Agent Skills + 3 slash commands + 10 production templates | Commands: /unity:new-script, /unity:optimize-scene, /unity:setup-test | Agents: @unity-scripter, @unity-refactor, @unity-performance, @unity-architect | Features: UI Toolkit templates (Editor + Runtime), automated code validation, scene optimization
Add the marketplace in Claude Code:
/plugin marketplace add https://github.com/Dev-GOM/claude-code-marketplace.git
Install plugins:
/plugin install hook-git-auto-backup@dev-gom-plugins
/plugin install hook-todo-collector@dev-gom-plugins
/plugin install hook-complexity-monitor@dev-gom-plugins
/plugin install hook-auto-docs@dev-gom-plugins
/plugin install hook-session-summary@dev-gom-plugins
/plugin install ai-pair-programming@dev-gom-plugins
/plugin install spec-kit@dev-gom-plugins
/plugin install unity-dev-toolkit@dev-gom-plugins
Restart Claude Code to load the plugins:
claude
# or
claude -r # Resume last session
# or
claude -c # Continue in current directory
Check plugin installation:
/plugin
/plugin marketplace add dev-gom-plugins ./path/to/.claude-plugin/marketplace.json
Once installed, the plugins work automatically:
/spec-kit:* commands to guide specification-driven development workflow/unity:* commands, invoke expert agents with @unity-*, and get automatic script validation through Agent SkillsEach plugin automatically creates a configuration file in .plugin-config/[plugin-name].json when first run. These files are preserved across plugin updates.
Common settings:
showLogs: Control Stop hook log visibility (false by default to reduce chat clutter)Example - Enable logs for TODO Collector:
Create or edit .plugin-config/hook-todo-collector.json:
{
"showLogs": true,
"outputDirectory": "",
"supportedExtensions": null,
"excludeDirs": null,
"commentTypes": null,
"outputFormats": null
}
For detailed configuration options:
Disable a specific plugin:
/plugin uninstall hook-git-auto-backup@dev-gom-plugins
Enable hook logs for a specific plugin:
Edit .plugin-config/[plugin-name].json and set "showLogs": true
Customize complexity thresholds: See Complexity Monitor Configuration
Add custom TODO patterns: See TODO Collector Configuration
The plugins generate the following files in your project root:
.todos-report.md - Detailed TODO report.todos.txt - Simple TODO list.complexity-log.txt - Complexity issues log.project-structure.md - Project structure documentation.session-summary.md - Session file operations summary.pair-programming-session.md - AI pair programming session reportPlugin configuration files (auto-generated in project root):
.plugin-config/ - Plugin-specific configuration files (preserves settings across plugin updates)Tip: Add output files to .gitignore if you don't want to commit them. Configuration files in .plugin-config/ should be committed to share settings with your team:
# Plugin output files
.todos-report.md
.todos.txt
.complexity-log.txt
.project-structure.md
.structure-state.json
.structure-changes.json
.session-summary.md
.pair-programming-session.md
.state/
# Optional: Uncomment to exclude plugin configs (if you don't want to share settings)
# .plugin-config/
Check plugin installation:
/plugin
Verify hooks are enabled in settings
Check Node.js is in PATH:
node --version
Ensure you're in a git repository:
git status
Check git is configured:
git config user.name
git config user.email
Adjust thresholds in the plugin configuration file to match your project's needs.
Each plugin has detailed technical documentation in its README:
Feel free to customize these plugins for your needs:
.claude-plugin directoryplugins/[plugin-name]/plugin.json if changing hook behavior/plugin validate .claude-pluginMIT License - feel free to use and modify for your projects.
Created for Claude Code to enhance developer productivity through automation.
Happy Coding! 🚀
For issues or suggestions, please open an issue on GitHub.
1.1.0