claude-code-plugin
CLAUDE.md1 starsChanged 4 months agoMITView on GitHub
This is a Claude Code plugin that provides commands for code review, PR creation, and multi-model second opinions via Gemini API. Commands: - /review-code - Code review (backed by code-reviewer skill) - /create-pr - PR creation (backed by pr-writer skill) - /create-feature - Feature definition via discussion (backed by feature-writer skill) - /create-issue - GitHub issue creation (backed by issue-creator skill) - /validate - Plan/architecture validation (backed by assumption-challenger, antipattern-detector, validator skills) - /gemini-review - Dual code review from Claude…
- Installs packages
In this repository19 other files it gives its agents.
- antipattern-detectorSkill
- architecture-reviewSkill
- assumption-challengerSkill
- cavemanSkill
- clipSkill
- code-reviewerSkill
- diagnoseSkill
- feature-writerSkill
- gemini-advisorSkill
- gemini-reviewerSkill
- grill-meSkill
- image-generatorSkill
- issue-creatorSkill
- paper-bananaSkill
- pr-writerSkill
- publishSkill
- tddSkill
- teach-meSkill
- validatorSkill
The file
We split this CLAUDE.md into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 116
Always check for lint/type errors before saying you're done:
- Very specific: line 118
TypeScript files: Run tsc --noEmit and check IDE diagnostics
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
This is a Claude Code plugin that provides commands for code review, PR creation, and multi-model second opinions via Gemini API.
Commands:
/review-code- Code review (backed bycode-reviewerskill)/create-pr- PR creation (backed bypr-writerskill)/create-feature- Feature definition via discussion (backed byfeature-writerskill)/create-issue- GitHub issue creation (backed byissue-creatorskill)/validate- Plan/architecture validation (backed byassumption-challenger,antipattern-detector,validatorskills)/gemini-review- Dual code review from Claude + Gemini (backed bygemini-reviewerskill)/ask-gemini- Second opinion from Gemini (backed bygemini-advisorskill)/generate-image- AI image generation with enhanced prompts (backed byimage-generatorskill)/paper-banana- Publication-quality illustrations via 5-agent pipeline (backed bypaper-bananaskill)/teach-me- Pedagogical code walkthrough (backed byteach-meskill)/grill-me- Stress-test a plan or design with relentless interviewing, persists decisions to CONTEXT.md and ADRs (backed bygrill-meskill)/publish- Convert markdown to portable, shareable HTML with syntax highlighting and tabs (backed bypublishskill)/tdd- Test-driven development with vertical slices (backed bytddskill)/diagnose- Structured debugging: reproduce first, guess never (backed bydiagnoseskill)/review-architecture- Review architecture for deepening opportunities (backed byarchitecture-reviewskill)/caveman- Activate ultra-compressed communication mode (backed bycavemanskill)/clip- Copy the last Claude message to the clipboard, cleaned and reformatted for md/Slack/plain/HTML (backed byclipskill)
Auto-triggering skills (no command):
assumption-challenger- Surfaces and stress-tests implicit assumptions in plans and proposalsantipattern-detector- Detects common failure patterns in proposals, architectures, and plans
Global skills (installed separately, available in all projects):
- Google Workspace CLI (
gws) skills — 40 skills, 10 personas, and 40 recipes for Gmail, Calendar, Drive, Sheets, Docs, Chat, Tasks, Meet, Keep, Forms, and more. Installed globally to~/.claude/skills/via:
Docs: https://github.com/googleworkspace/clinpm install -g @googleworkspace/cli # Install the CLI gws auth setup # Configure OAuth (requires gcloud CLI) npx skills add https://github.com/googleworkspace/cli # Install agent skills
Architecture
.claude-plugin/plugin.json # Plugin metadata (name, version, author)
commands/ # Slash command definitions (Markdown with YAML frontmatter)
skills/ # Skill implementations (SKILL.md files)Commands define user-facing slash commands with:
- YAML frontmatter:
description,argument-hint,allowed-tools - Workflow instructions in Markdown
- Template variables:
$ARGUMENTScontains text passed after the command
Skills define reusable capabilities that commands invoke:
- YAML frontmatter:
name,description - Detailed instructions for how to perform the skill
Plugin File Patterns
Command files (commands/*.md)
---
description: "Short description shown in command list"
argument-hint: "[optional-arg]"
allowed-tools: ["ToolName", "Bash(pattern:*)"]
---Skill files (skills/<name>/SKILL.md)
---
name: skill-name
description: |
Multi-line description of when to use this skill
---TypeScript Infrastructure
- TypeScript (
src/): Hooks, config, Gemini API, HUDsrc/gemini/— Gemini text generation API wrapper (@google/genaiSDK, CLI entrypoint atdist/gemini/cli.js)src/image-gen/— Gemini image generation API wrapper (CLI entrypoint atdist/image-gen/cli.js)src/publish/— Markdown-to-HTML converter with shiki syntax highlighting and tabbed navigation (CLI entrypoint atdist/publish/cli.js)src/clip/— Claude Code output reformatter for clipboard pasting: md/slack/plain/html modes (CLI entrypoint atdist/clip/cli.js)
Build & Test
npm install # Install TypeScript toolchain
npm run build # Compile src/ -> dist/
npm run test # Run vitest tests
npm run lint # ESLint (no any allowed)
npm run typecheck # tsc --noEmit
npm run check # All three: typecheck + lint + testHook Scripts (scripts/*.mjs)
Standalone Node.js scripts invoked by Claude Code via hooks/hooks.json.
These use only Node.js builtins (no imports from dist/ or node_modules/).
The TypeScript equivalents in src/hooks/ provide the same logic in testable form.
Hook Contract
stdin → JSON { sessionId, directory, prompt?, toolName? }
stdout → JSON { continue: true/false, message?, hookSpecificOutput? }Version Management
Single source of truth: .claude-plugin/plugin.json — bump the version there when making changes (minor for new features/commands, patch for fixes). Do not edit versions in package.json or .claude-plugin/marketplace.json — both are automatically synced from plugin.json via scripts/sync-version.mjs each time npm run build runs.
Before Completing Tasks
Always check for lint/type errors before saying you're done:
- TypeScript files: Run
tsc --noEmitand check IDE diagnostics - Use
mcp__ide__getDiagnosticsto check for red squiggles in the IDE
Fix all errors before marking a task complete.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

