ln-115-devops-docs-creator

Generate a runbook.md for Docker-based DevOps setup, deployment, and troubleshooting.

534|73|Updated Oct 24, 2025
One-click install
npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-115-devops-docs-creator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ln-115-devops-docs-creator
Source: https://github.com/levnikolaevich/claude-code-skills/tree/main/ln-115-devops-docs-creator
Command: npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-115-devops-docs-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill conditionally creates runbook.md for DevOps setups when a project has Docker or deployment config, enabling automated, repeatable setup and troubleshooting guidance.

Core Features & Use Cases

  • Conditional invocation when hasDocker is true
  • Generates runbook.md with setup, deployment, troubleshooting sections
  • Reuses context data from ln-110-project-docs-coordinator
  • Prunes content based on deployment targets, GPUs, and services
  • Validates structure and maintenance sections

Quick Start

Run ln-115-devops-docs-creator in projects with Docker configuration to produce docs/project/runbook.md.

Frequently Asked Questions about ln-115-devops-docs-creator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a DevOps runbook for Docker projects?

A runbook documents step-by-step setup, deployment, and troubleshooting procedures. This Skill generates runbook.md automatically when Docker configuration is detected, pulling setup instructions, deployment steps, and troubleshooting guidance from your docker-compose.yml and .env.example files to ensure consistent, repeatable operations.

When should I use a runbook for Docker deployment?

Use a runbook when you have Docker or deployment configuration in your project. It solves the problem of inconsistent deployment procedures and missing troubleshooting documentation by automatically generating comprehensive guides that reflect your actual Docker services, environment variables, and deployment targets.

Can I customize the runbook based on deployment scale and GPU requirements?

Yes. The runbook conditionally prunes content based on DEPLOYMENT_SCALE, HAS_GPU, and available DOCKER_SERVICES parameters. This ensures your documentation reflects only the relevant setup and troubleshooting steps for your specific infrastructure configuration.

What data does the runbook pull from my project?

The runbook extracts configuration from docker-compose.yml and .env.example files, along with context data from your project documentation coordinator. It generates sections for setup, deployment, and troubleshooting while remaining idempotent across regenerations.

Do I need to manually update the runbook each time my Docker config changes?

No. The Skill is idempotent, meaning you can regenerate runbook.md whenever your Docker configuration or deployment setup changes, and it automatically reflects the current state without manual edits or merge conflicts.

What's the difference between a runbook and general project documentation?

A runbook is operationally focused—it documents how to perform specific tasks like deploying, scaling, and troubleshooting in your environment. This Skill creates runbooks specifically tailored to your Docker and deployment configuration, distinct from architecture or feature documentation.