Playbooks Plugin

Structured prompt templates for Claude Code. PR reviews, release notes, audits, blog posts, and more.

The Problem

You use Claude for repetitive tasks—reviewing PRs, writing release notes, auditing code—but get inconsistent results because you write prompts from scratch each time.

The Solution

Pre-built, battle-tested prompt templates that produce structured, actionable output every time.

Install

Inside Claude Code, run:

/plugin install andreolf/playbooks-plugin

Done! Start using any skill immediately.

Skills

How It Works

You: "/review-pr" + paste diff

              ↓

┌─────────────────────────────────────────┐
│  Playbooks Plugin                       │
│  → Loads review-pr skill template       │
│  → Applies structured output rules      │
│  → Enforces consistent format           │
└─────────────────────────────────────────┘

              ↓

Claude: Structured review with:
        • Summary (3 bullets)
        • High/Medium/Low risk issues
        • Test plan
        • Follow-up suggestions

Key features:

• Each skill enforces a specific output schema
• Deterministic: same input produces consistent structure
• Never forgets key sections (test plans, upgrade notes, etc.)
• Works with any codebase or context

Example Usage

PR Review

/review-pr

Review this authentication change:

diff --git a/src/auth.ts b/src/auth.ts
+ import bcrypt from 'bcrypt';
+ const hash = await bcrypt.hash(password, 10);
...

Output includes:

• Summary bullets
• Risk-categorized issues with fixes
• Test plan (unit, integration, edge cases)
• Suggested follow-ups

Release Notes

/release-notes

Product: MyApp
Version: 2.0.0

Changes:
- Added dark mode support
- Fixed login timeout after 30 mins
- Deprecated /api/v1 endpoints
- Breaking: Changed auth token format

Output includes:

• Executive summary
• Categorized changelog (Added/Fixed/Breaking/etc.)
• Upgrade steps and gotchas
• Announcement copy (Twitter, blog, dev-focused)

Blog Post

/ship-blog

Topic: Why we rewrote our auth system in Rust
Audience: Backend engineers
Angle: Performance gains with real benchmarks

Output includes:

• 5 title options
• Hook line (140 chars)
• Full outline (H2/H3)
• 800-1200 word draft
• TLDR bullets
• 7-tweet X thread
• 3 CTA variants

When to Use Playbooks

✅ Use for:

• PR reviews that need consistent structure
• Release notes with proper changelog format
• Blog posts with full distribution package
• Security audits with Go/No-Go decisions
• Any task where you want repeatable quality

❌ Skip for:

• Simple one-off questions
• Tasks without a standard output format
• Creative writing that needs to be freeform

Customization

Each skill is a markdown file in skills/*/SKILL.md. Fork the repo to:

• Modify output schemas
• Add new skills
• Adjust rules for your workflow

Development

git clone https://github.com/andreolf/playbooks-plugin
cd playbooks-plugin

# Test locally
claude --plugin-dir /path/to/playbooks-plugin

Contributing

PRs welcome! To add a new skill:

1. Create skills/your-skill/SKILL.md
2. Follow the existing skill format (frontmatter + rules + output schema)
3. Test with Claude Code
4. Submit PR

License

MIT — see LICENSE

Acknowledgments

Inspired by claude-playbooks, the CLI version of this concept.

Get consistent, professional output from Claude — every time.