runbook-generator
Generate operational runbooks from a service name — deployment, incident response, maintenance, and rollback workflows. Templated structure customizable per environment. Use when documenting on-call procedures for a new service, standardizing incident response across teams, or producing runbooks before launching to production.
What this skill does
# Runbook Generator **Tier:** POWERFUL **Category:** Engineering **Domain:** DevOps / Site Reliability Engineering --- ## Overview Generate operational runbooks quickly from a service name, then customize for deployment, incident response, maintenance, and rollback workflows. ## Core Capabilities - Runbook skeleton generation from a CLI - Standard sections for start/stop/health/rollback - Structured escalation and incident handling placeholders - Reference templates for deployment and incident playbooks --- ## When to Use - A service has no runbook and needs a baseline immediately - Existing runbooks are inconsistent across teams - On-call onboarding requires standardized operations docs - You need repeatable runbook scaffolding for new services --- ## Quick Start ```bash # Print runbook to stdout python3 scripts/runbook_generator.py payments-api # Write runbook file python3 scripts/runbook_generator.py payments-api --owner platform --output docs/runbooks/payments-api.md ``` --- ## Recommended Workflow 1. Generate the initial skeleton with `scripts/runbook_generator.py`. 2. Fill in service-specific commands and URLs. 3. Add verification checks and rollback triggers. 4. Dry-run in staging. 5. Store runbook in version control near service code. --- ## Reference Docs - `references/runbook-templates.md` --- ## Common Pitfalls - Missing rollback triggers or rollback commands - Steps without expected output checks - Stale ownership/escalation contacts - Runbooks never tested outside of incidents ## Best Practices 1. Keep every command copy-pasteable. 2. Include health checks after every critical step. 3. Validate runbooks on a fixed review cadence. 4. Update runbook content after incidents and postmortems.
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.