Runbook Generator

To generate an operational runbook, this Skill analyzes codebase signals to detect your CI/CD, database, hosting, and framework components, then produces detailed procedures for deployment, incident response, and database maintenance. It supports generating runbooks for stacks like Next.js and PostgreSQL hosted on Vercel.

Runbook staleness detection works by linking specific runbook sections to your configuration files. When those configuration files are modified, the system flags the associated runbook sections as outdated, ensuring your operational procedures remain accurate during audits or onboarding.

Yes, you can create incident response procedures for a specific framework. The automated stack detection identifies your framework and hosting environment, then generates production-grade incident response runbooks tailored to your application's specific operational requirements.

Deployment runbooks include testing methodologies such as staging dry-runs and quarterly reviews. These procedures ensure your deployment, incident response, and database maintenance documentation remains reliable and production-ready over time.

The best way to maintain SRE documentation is to automate runbook generation with staleness detection. By linking documentation sections to configuration files, the system automatically flags outdated procedures when deployment or database configurations change.

No specific database or hosting platform is required. The automated stack detection analyzes your codebase to identify your database and hosting components, generating database maintenance runbooks tailored to your specific infrastructure, including PostgreSQL and Vercel.