Claude Code Plugins for Library Maintainers

A collection of Claude Code plugins for library maintainers and developers.

Why these plugins — a thin governance layer, not a heavier harness

As mainstream harness / loop-engineering tooling grows heavier — an "OS wrapped around the model" — these plugins make the opposite bet: stay thin and ride Claude Code's native loop, tools, and context management, adding only the judgment a generic harness cannot supply. A custom layer is always slower to evolve than the harness beneath it, so the goal is to fill gaps, never fence off native features.

Three governing principles (the plugin's constitution):

• Minimal Intervention — hook around the native loop, never rewrite it. The thinner the layer, the longer it lives.
• Critical but Constructive (Rule of Law) — a maintainer, not a typist. Human instructions sit below the project's constitution (philosophy, architecture, design docs); a conflict triggers a documented amendment — revise the instruction, or amend the doc — never silent compliance and never unilateral override. Unobserved data stays "unknown" rather than guessed.
• Adaptive Iteration — don't stop at "it compiles". When primary work is done, surplus cycles climb a lifecycle ladder: durable value → stability → efficiency.

How that differs from the mainstream:

	Mainstream harness / loop tooling	iyu
Stance	Wrap the model in an OS	Thin layer on Claude Code native
Human instruction	Ground truth to execute	Below the project constitution; corrected via amendment
Termination	Stops at delivery (compiles / marker hit)	Climbs the lifecycle ladder past delivery
Feedback loop	Ends at merge	Closed — production telemetry (App Insights) flows back to the backlog

Quick Start

# Add the marketplace
/plugin marketplace add iyulab/claude-plugins

# Install the iyu plugin
/plugin install iyu@iyulab-plugins

Available Plugins

Versioning — two independent version numbers exist by design: marketplace.json → metadata.version tracks the marketplace registry (structure of this catalog), while each plugin's plugin.json → version tracks that plugin itself. They advance separately. Per-plugin keywords are sourced from plugin.json and mirrored into the marketplace entry. See CHANGELOG.md for the iyu plugin history.

iyu (v1.15.0)

Productivity toolkit for open-source library maintainers — adaptive iterative development, issue triage, PR review

Component	Type	Activation	Description
mindset	Skill	Auto (background)	"Critical but Constructive" mindset for conversational triage/dev discussions
issue-triage	Skill	Auto (conversational)	Decision matrices and triage advice
/iyu:issue	Skill	Manual	Full issue triage report
/iyu:pr	Skill	Manual	PR review with security focus
/iyu:run	Skill	Manual	Plan-driven development execution
/iyu:run-cycle	Skill	Manual	Adaptive iterative cycles (re-plan → execute → verify → reflect)
/iyu:telemetry-az	Skill	Manual	Azure App Insights telemetry triage — defects, regressions, feature drop

Installation

/plugin install iyu@iyulab-plugins

Skills (Auto-Activated)

The plugin automatically activates when you discuss issue evaluation or PR review. Just ask naturally:

• "Should I accept this feature request?"
• "How should I respond to this issue?"
• "Is this in scope for my project?"
• "Help me triage this pull request"
• "Review this PR for me"
• "Find similar bugs in the codebase"

Commands

Command	Description
/iyu:issue	Systematic issue evaluation with root cause analysis
/iyu:pr	Professional PR review with security awareness
/iyu:run	Plan-driven development execution
/iyu:run-cycle	Adaptive iterative development cycles
/iyu:telemetry-az	Azure App Insights telemetry triage and issue discovery

/iyu:issue

# Triage a GitHub issue
/iyu:issue https://github.com/user/repo/issues/123

# Quick decision only
/iyu:issue https://github.com/user/repo/issues/123 --quick

# Triage and save report
/iyu:issue ./docs/feature-request.md --save

/iyu:pr

# Full PR review
/iyu:pr https://github.com/user/repo/pull/123

# Quick review (critical issues only)
/iyu:pr https://github.com/user/repo/pull/123 --quick

# Security-focused review
/iyu:pr https://github.com/user/repo/pull/123 --security-focus

/iyu:run

# Auto-detect next phase from roadmap
/iyu:run

# Input-driven task execution
/iyu:run "Implement caching layer for API"

# Plan only, no execution
/iyu:run --dry-run

/iyu:run-cycle

# 5 adaptive cycles (default)
/iyu:run-cycle

# up to 10 cycles (N is a ceiling, not a target)
/iyu:run-cycle 10

# Preparation + phase backlog only
/iyu:run-cycle 5 --dry-run

Each cycle runs Re-plan → Design → Execute → Verify → Reflect → Derive-Next. Just-in-time scoping: only the current cycle is scoped concretely, and each cycle's outcome decides the next cycle's scope. The roadmap is a phase backlog — it never assigns scope to numbered cycles, so the run behaves like genuine multi-turn work rather than one upfront N-cycle plan.

/iyu:telemetry-az

# Analyze Azure Application Insights since the last run, triage, and file issues
/iyu:telemetry-az

# Override the window start
/iyu:telemetry-az --since 2026-05-01T00:00:00Z

# Collect + triage + print report only (no files written, watermark not advanced)
/iyu:telemetry-az --dry-run

# Write the report but create no issue files
/iyu:telemetry-az --no-issues

Reads per-repo settings from claudedocs/telemetry/config.json (App Insights app id + thresholds), resumes from a dedicated watermark file, classifies defects / performance regressions / feature-drop signals, runs issue-triage "1 → 10" discovery aligned with the project philosophy, and files issues only for threshold-crossing findings. Requires az login.

Decision Matrices

Issue Triage:

	Philosophy Aligned	Philosophy Misaligned
High Feasibility	✅ ACCEPT	↗️ REDIRECT
Medium Feasibility	🔄 ADAPT	⏳ DEFER / ↗️ REDIRECT
Low Feasibility	⏳ DEFER	❌ DECLINE

PR Review:

Severity	Meaning
🔴 Blocker	Must fix before merge
🟠 Major	Should fix, or maintainer fixes post-merge
🟡 Minor	Nice to have, non-blocking
✨ Praise	Celebrate good work

Read more about iyu plugin

Philosophy

"Every issue is an opportunity" - Our plugins help maintainers move beyond simple accept/reject decisions to find the best path forward for their projects.

Marketplace Management

# List configured marketplaces
/plugin marketplace list

# Update marketplace metadata
/plugin marketplace update iyulab-plugins

# Remove marketplace
/plugin marketplace remove iyulab-plugins

# List installed plugins
/plugin list

Contributing

1. Fork this repository
2. Create your plugin in plugins/your-plugin-name/
3. Add plugin.json, commands/, skills/, or agents/ as needed
4. Update .claude-plugin/marketplace.json
5. Submit a PR

Plugin Structure

plugins/
└── your-plugin/
    ├── .claude-plugin/
    │   └── plugin.json       # Plugin metadata (required)
    ├── commands/             # Slash commands
    │   └── command-name.md
    ├── skills/               # Auto-activating skills
    │   └── skill-name/
    │       └── SKILL.md
    ├── agents/               # Custom agents (optional)
    └── README.md             # Documentation

Requirements

• Claude Code CLI installed
• Claude Code version with plugin support

License

MIT - See LICENSE for details.

Links

• Claude Code Documentation
• Plugin Development Guide
• Iyulab GitHub