Claude Plugins Marketplace
Personal Claude Code plugins for development workflows.
See WORKFLOW.md for how to use these plugins together across the development lifecycle, and CONNECTORS.md for which plugins integrate with which external systems (GitHub gh CLI, ClickUp MCP, etc.).
Installation
# Add this marketplace
/plugin marketplace add juanmhidalgo/claude-plugins
# Or from local path
/plugin marketplace add /path/to/claude-plugins
Available Plugins
code-review
Comprehensive code review workflow with skeptical AI feedback triage.
Commands:
/code-review/branch - Review branch vs base/code-review/staged - Review staged changes/code-review/triage - Triage AI feedback (Copilot, Gemini)/code-review/dismiss - Dismiss false positives on GitHub/code-review/fixes-plan - Generate fix tracking document/code-review/implement-fix - Implement fixes, asking for technical decisions/code-review/mark-fixed - Verify and mark fixes/code-review/resolve-fixed - Resolve GitHub threads for fixed issues
Install:
/plugin install code-review@juanmhidalgo-plugins
prd-toolkit
Create and manage Product Requirements Documents (PRDs) with AI assistance.
Commands:
/prd:refine [file | issue-url] - Improve existing PRD or convert vague issue to PRD/prd:validate [file | issue-url] - Verify implementation matches PRD criteria/prd:analyze [file | issue-url | text] - Identify gaps, edge cases, and ambiguities
For creating new specs from scratch, use /feature-dev:spec.
Install:
/plugin install prd-toolkit@juanmhidalgo-plugins
discuss
Critical feature discussion, idea refinement, and adversarial review of technical documents.
Commands:
/discuss:feature [feature or idea] - Critical analysis, identify gaps and risks/discuss:brainstorm [problem] - Generate 4-6 alternative approaches/discuss:challenge [proposal] - Argue against to stress-test/discuss:tradeoffs [A vs B] - Compare options with pros/cons matrix/discuss:adversarial-doc-review [doc-path] - Red-team a written PRD/ADR/spec in a fresh context, reporting only what would cause a bad design decision/discuss:grill [plan or idea] - Interview you in rounds, each question with a recommended answer, until every decision is settled/discuss:wait-what [the part that lost you] - Re-explain the last message simply, in the conversation's language
Install:
/plugin install discuss@juanmhidalgo-plugins
intake
Translate unstructured customer/CSM/Sales/Support requests into engineering signals: feasibility reports, customer-facing reply drafts, and anticipated-objection Q&A. Sits before /discuss:feature and /feature-dev:spec in the workflow.
Commands:
/intake:feasibility <request or path> - Decompose a customer ask into capabilities + constraints, research each in parallel against the codebase, produce a Status × Effort × Evidence map with risk callout, phased recommendation, and Excluded for this customer list/intake:respond-draft <report> - Summarize a feasibility report for CSM in plain language. No customer-facing draft (CSM owns customer voice); no calendar commitments (uses commitment categories and [CSM TO CONFIRM TIMELINE] placeholders)/intake:objection-prep <report> - Anticipate CSM/Sales/customer pushback against a feasibility report; outputs a Q&A list with prepped factual responses
Install:
/plugin install intake@juanmhidalgo-plugins
retro
Session retrospectives built on what the Claude Code logs actually measured — cost, wall clock, permission denials, hook blocks, slowest turns — instead of asking how the session felt. Every finding names the file that fixes it.
Commands:
/retro:session [--last N] [--session <id>] - Digest this project's session logs, rank the friction by what it cost, and route each finding to a destination: a CLAUDE.md rule, a memory file, a permission rule, a hook, or a fix to a plugin in this repo. Scoped to one project per run
Install:
/plugin install retro@juanmhidalgo-plugins
Updating Plugins
# Refresh marketplace metadata
/plugin marketplace update juanmhidalgo-plugins
# Reinstall to get latest version
/plugin uninstall code-review@juanmhidalgo-plugins
/plugin install code-review@juanmhidalgo-plugins
Requirements
gh CLI installed and authenticated- GitHub token with repo scope
Recommended permissions
These plugins use git, gh, and standard test-runner CLIs heavily. To avoid per-call permission prompts, merge the rules from settings.example.json into your ~/.claude/settings.json (user-wide) or the project-level .claude/settings.json. The example also denies common destructive operations (rm -rf, git push --force, git reset --hard) and reads against .env/credentials paths.
Disclaimer
This is a community project and is not affiliated with, endorsed, or supported by Anthropic.
These plugins are provided "as is" without warranty of any kind. Use at your own risk. The author is not responsible for any damages or issues arising from the use of these plugins.
License
MIT License - See LICENSE for details.
