Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By lpasqualis
Audits and optimizes Claude Code configurations—commands, agents, workers, and CLAUDE.md files—while automating Git workflows, documentation generation, and code quality checks through reusable templates and parallel verification agents.
npx claudepluginhub lpasqualis/lpclaude --plugin lpclaude-configAnalyze project's commands, subagents, and workers to identify needed conversions and optimizations
Audits and optimizes CLAUDE.md files against current best practices, extracting inappropriate content to external docs
Add parallel execution capabilities to existing Claude Code commands
Create new Claude Code commands with best practices and automatic validation
Optimize slash command definitions for best practices and performance
Meticulous completion verification specialist that rigorously verifies whether claims about task completion are actually true. Expert at identifying incomplete implementations, missing tests, stubbed code, and premature completion declarations. Use ONLY when explicit verification is requested or definitive completion claims are made about deliverables. Invoke when user explicitly asks to "verify completion", "check if implementation is done", "confirm feature is complete", or makes declarative statements like "X is finished/implemented/ready". Do NOT trigger on planning discussions, status questions, or casual mentions of completion words. Use proactively when actual verification or validation is clearly needed.
Expert LLM delegation specialist that seamlessly connects to external language models including GPT-4, GPT-3.5, Gemini, Ollama, and local models via the llm bash tool. Invoke this agent to delegate tasks, get second opinions, validate solutions, or continue existing model conversations. Use when users mention external LLMs, API models, delegation, validation with other models, checking work, comparing responses across models, or need specific model capabilities. MUST BE USED PROACTIVELY when detecting phrases like "use gpt", "ask gemini", "check with", "delegate to", "second opinion", "validate with", "compare using", "continue conversation", "external model", "api model", or references to specific providers.
An expert documentation specialist that comprehensively audits and updates project documentation for accuracy, relevance, and consistency with the current codebase. Invoke this agent when documentation is outdated, inconsistent, or needs comprehensive review after code changes or refactoring. Use when you need to identify documentation gaps, fix inaccurate information, consolidate redundant docs, or ensure documentation reflects the current state of the project. This agent systematically analyzes code-to-documentation alignment, validates examples and instructions, and produces a detailed audit report with all necessary corrections. Use proactively when appropriate.
Expert implementation plan auditor for reviewing implans for completeness, correctness, and compliance with requirements. Use proactively when users mention implan auditing, plan validation, checking for incomplete implementations, stubs, TODOs, missing test coverage, or when they need to verify implementation completeness. Analyzes both implan structure and associated codebase to detect gaps, placeholder code, untested functionality, and deviations from requirements. Outputs comprehensive audit reports with corrective actions and creates specialized testing phases for critical untested areas.
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Interactive setup wizard for configuring any repository with Claude Code best practices, based on Boris Cherny's workflow
Claude Code workflow patterns: prompting, CLAUDE.md maintenance, multi-agent orchestration
Opinionated workflow guides and best practices - the preacher's proven patterns for Claude Code projects
Git and PR workflows with code review, onboarding, and PR enhancement
Commands for loading context and priming Claude for specific tasks
Complete collection of battle-tested Claude Code configs from an Anthropic hackathon winner - agents, skills, hooks, and rules evolved over 10+ months of intensive daily use
No model invocation
Executes directly as bash, bypassing the AI model
No model invocation
Executes directly as bash, bypassing the AI model
Share bugs, ideas, or general feedback.
This is my personal Claude Code configuration that I maintain in Git. I'm sharing it publicly as an example of how to organize and version-control a Claude Code setup. This system works for me and my needs, but might not work for others. My requirements are:
What this is: My personal collection of agents, slash commands, and tools that I use across all my projects.
What this isn't: A framework or product to install. It's one person's configuration shared as a reference.
Claude Code supports personal configurations via ~/.claude/, but there aren't many examples of how to organize and maintain them. This repository shows:
The easiest way to use this configuration is via Claude Code's plugin system.
Quick Install:
/plugin and select "Add marketplace"https://github.com/lpasqualis/lpclaude/plugin again and select "Install plugin"lpclaude-config from the listOr use commands directly:
# Step 1: Add the marketplace (HTTPS format recommended)
/plugin marketplace add https://github.com/lpasqualis/lpclaude
# Step 2: Install the plugin
/plugin install lpclaude-config
Or skip the marketplace and install directly:
/plugin install https://github.com/lpasqualis/lpclaude
Benefits:
~/.claude/ configsSee PLUGIN_INSTALL.md for detailed plugin documentation.
For full control over files and symlinks:
git clone https://github.com/lpasqualis/lpclaude.git ~/.lpclaude
cd ~/.lpclaude
./setup.sh
See "If You Want to Try My Components" section below for details.
Not ready to install? You can also:
Browse the repository to:
If you find something useful:
~/.claude/ directoryTo create your own configuration repository:
Here's what I've built for my workflow (yours will be different):