By lucasmccomb
Seven-lens plan-quality gate. Before a plan, spec, or requirements doc ships to execution, /document-review fans out to 7 role-specific reviewer agents (coherence, feasibility, product-lens, scope-guardian, design-lens, security-lens, adversarial) and merges structured JSON findings with severity and confidence. Each lens has tight what-you-flag boundaries so they do not overlap.
Reviews a plan, spec, or design doc by attacking its premises. Applies four tests - falsification, reversal cost, decision-scope mismatch, abstraction audit - to surface unstated assumptions, weak foundations, and decisions the author has not realized they are making. Challenges premises rather than details. Returns structured JSON findings with severity and confidence.
Reviews a plan, spec, or design doc for internal consistency. Flags contradictions between sections, dangling references, step ordering errors, undefined terms, and scope/detail mismatches. Returns structured JSON findings with severity and confidence. Does not judge feasibility, scope, or security - only whether the document agrees with itself.
Reviews a plan, spec, or design doc for software design quality. Flags fragile coupling, leaky abstractions, mixed responsibilities, awkward data flow, unnecessary state, and patterns that will be painful to change. Returns structured JSON findings with severity and confidence. Does not judge feasibility, scope, or security - only whether the proposed shape will be a good shape to live with.
Reviews a plan, spec, or design doc for whether it can actually be built as described. Flags missing prerequisites, technology misuse, unrealistic timelines, unavailable dependencies, and unbuildable steps. Returns structured JSON findings with severity and confidence. Does not judge whether the plan is a good idea - only whether it is executable.
Reviews a plan, spec, or design doc from a product perspective. Flags missing user stories, unclear success criteria, undefined metrics, UX gaps, and misalignment between stated goals and proposed implementation. Returns structured JSON findings with severity and confidence. Does not judge feasibility, scope, or security - only whether the plan serves a user and knows when it has succeeded.
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.
Modular configuration system for Claude Code - pick the modules you want, install in seconds. Works with Claude Code CLI, VS Code, Cursor, the macOS Claude app, and any other editor with Claude Code support.
CCGM is a curated collection of 71 configuration modules for Claude Code. Instead of hand-crafting rules, hooks, commands, and permissions from scratch, you pick modules and install them with a single command.
Each module is self-contained with its own README, so you can also copy individual files manually without the installer.
CCGM places files into ~/.claude/ (global) or .claude/ (project-level):
| Directory | What | How Claude Uses It |
|---|---|---|
rules/*.md | Behavior rules | Loaded automatically at session start |
commands/*.md | Slash commands | Available as /commit, /pr, etc. |
agents/*.md | Subagent prompts | Reusable prompts invoked by commands and skills via the Task tool |
hooks/*.py | Workflow hooks | Triggered on Claude Code events |
settings.json | Permissions | Controls tool access and auto-approval |
Paste the block below into a fresh Claude Code session. The agent detects your environment, picks a preset, runs the installer, and reports what was installed. No flags, no shell environment to configure first.
Install CCGM (Claude Code God Mode) for me.
Steps:
1. Detect my OS (uname -s), shell ($SHELL), and home directory ($HOME).
2. Clone the repo if it does not already exist:
git clone https://github.com/lucasmccomb/ccgm.git ~/code/ccgm
If it already exists, pull the latest main:
cd ~/code/ccgm && git fetch origin && git checkout main && git pull --ff-only origin main
3. Read the available presets: ls ~/code/ccgm/presets/
Available presets and what they include:
- minimal : global-claude-md, autonomy, git-workflow
- standard : the above + identity, hooks, settings, commands-core, commands-utility
- team : standard core + github-protocols, code-quality, systematic-debugging, verification
- cloud-agent : large set for power users running autonomous agents
- full : every stable module
Based on what you know about my workflow, recommend one preset. Ask me to confirm or pick a different one before continuing. (One question only — do not ask anything else.)
4. Check what is already installed by looking at ~/.claude/rules/, ~/.claude/commands/, ~/.claude/hooks/. List any CCGM files already present and note you will skip overwriting them.
5. Read ~/.claude/settings.json if it exists and note its content. The installer will merge non-destructively — it will not delete keys that are already there.
6. Run the installer:
cd ~/code/ccgm
CCGM_NON_INTERACTIVE=1 \
CCGM_USERNAME="$(gh api user --jq '.login' 2>/dev/null || echo '')" \
./start.sh --preset <chosen-preset>
7. Verify the install succeeded by checking that these paths exist:
~/.claude/rules/
~/.claude/CLAUDE.md (if global-claude-md was in the preset)
List the files now present in ~/.claude/rules/ and ~/.claude/commands/.
8. Report: which preset was installed, which modules were skipped (already present), and any errors.
For blocks pre-selecting a specific preset, and for how to dry-run this safely, see docs/install-via-agent.md.
npm install -g @anthropic-ai/claude-code)The installer checks for Claude Code, additional tools (jq, Python 3, gh CLI), and offers to install any that are missing.
git clone https://github.com/lucasmccomb/ccgm.git
cd ccgm
./start.sh
The interactive setup handles everything: prerequisite checks, module selection, and configuration. No flags needed.
npx claudepluginhub lucasmccomb/ccgm --plugin document-reviewCaptures permission events, tool failures, and user-correction signals; runs a daily analyzer via direct Anthropic API call; produces a local digest + opt-in Resend email; opt-in real-time security alerts and opt-in confidence-gated auto-apply. Cross-clone-safe via fcntl file locks. Webhook publisher seam is dormant by default.
Spec-driven development where E2E vision specs define target behavior. /atdd reads Playwright specs, iteratively builds app code until all tests pass, then ships.
/brainstorm - hard gate that forbids code, scaffolding, or implementation until a design spec is written and user-approved. Proposes 2-3 approaches with tradeoffs, writes a design doc, self-reviews for TBDs and contradictions, then hands off to /xplan. Pairs with /ideate (which refines the concept) to enforce spec-before-plan-before-code.
Configure Claude as a fully autonomous Staff-level engineer who executes tasks end-to-end without asking unnecessary questions.
/adrev - adversarial review of a plan or any entity (file, doc, PR, issue, directory, or stated concept). Dispatches a separate adrev-reviewer agent that attacks premises, hunts failure modes, and steelmans the case against. Plan targets get findings incorporated into the plan automatically unless told not to; all other targets get a report.
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
v9.44.1 — Patch release for Gemini environment/version detection and qwen auth gating. Run /octo:setup.
Develop, test, build, and deploy Godot 4.x games with Claude Code. Includes GdUnit4 testing, web/desktop exports, CI/CD pipelines, and deployment to Vercel/GitHub Pages/itch.io.
Comprehensive PR review agents specializing in comments, tests, error handling, type design, code quality, and code simplification
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
A growing collection of Claude-compatible academic workflow bundles. Covers scientific figures, manuscript writing and polishing, reviewer assessment, citation retrieval, data availability, paper reading, literature search, response letters, paper-to-PPTX conversion, and evidence-grounded Chinese invention patent drafting. Rules are organized as reusable skill folders with explicit workflows and quality checks.