By gonzaloetjo
Iteratively generates and refines CLAUDE.md files using sequential agents with fresh context windows — invents dev tasks, plans them, discovers missing context, and refines the CLAUDE.md.
Configure settings for the CLAUDE.md generator — iteration count, interaction mode, focus areas, and output preferences.
Iteratively refines an existing CLAUDE.md file using stress-test refinement with sequential agents. Spawns a fresh agent for each iteration — each gets a clean context window. Requires an existing CLAUDE.md (run /init first). Run /setup-claude-md:configure to set options.
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.
npx claudepluginhub gonzaloetjo/setup-claude-mdMulti-stage parallelized per-function audit for Solidity contracts with human-in-the-loop review. Discovers functions, captures design decisions, runs 3 analysis stages, then presents findings for developer classification and re-evaluation of disputed items.
Non-interactive eval variant of solidity-function-audit. Removes all interactive prompts for automated evaluation via claude -p mode. Reads design decisions from GROUND_TRUTH.md, skips Slither, always runs verification, stops after Verification (no Stage 4/5).
Agent team variant of solidity-function-audit with human-in-the-loop review. Uses agent teams for inter-agent messaging, shared task list with dependencies, plus interactive design decision capture, findings review, and dispute re-evaluation. Requires CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1.
CLAUDE.md lifecycle toolkit: initialise, enhance, sync, and modularise CLAUDE.md files with a 150-line cap, automatic chaining, and Karpathy behavioural guardrails.
Optimize CLAUDE.md and docs/ ecosystem following Boris Cherny's best practices
llmdoc Claude Code plugin with init, update modes, temporary investigation cache, and use
Use this agent when you need to analyze a service or codebase component and create comprehensive documentation in CLAUDE.md files. This agent should be invoked after implementing new services, major refactoring, or when documentation needs updating to reflect the current codebase structure. Examples: <example>Context: The user has just implemented a new authentication service and wants to document it properly. user: 'I just finished implementing the auth service, can you document how it works?' assistant: 'I'll use the codebase-documenter agent to analyze the authentication service and create detailed documentation in CLAUDE.md' <commentary>Since the user has completed a service implementation and needs documentation, use the Task tool to launch the codebase-documenter agent to create comprehensive CLAUDE.md documentation.</commentary></example> <example>Context: The user wants to ensure a newly added API module is properly documented for the team. user: 'We need documentation for the new payment processing API I just added' assistant: 'Let me use the codebase-documenter agent to analyze the payment processing API and create proper documentation' <commentary>The user needs documentation for a new API module, so use the codebase-documenter agent to create CLAUDE.md files with setup instructions and architectural notes.</commentary></example>
Tools to maintain and improve CLAUDE.md files - audit quality, capture session learnings, and keep project memory current.
Make a codebase agent-ready by scaffolding AGENTS.md, ARCHITECTURE.md, and docs/ structure following progressive disclosure patterns. Creates CLAUDE.md as a symlink for Claude Code compatibility.