compiling-devops-agent

Generate project-specific DevOps agent files with YAML frontmatter for detected infrastructure tools.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/pipemind-com/pipemind-marketplace --skill compiling-devops-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: compiling-devops-agent
Source: https://github.com/pipemind-com/pipemind-marketplace/tree/main/plugins/spec-driven-development/skills/compiling-devops-agent
Command: npx skills add https://github.com/pipemind-com/pipemind-marketplace --skill compiling-devops-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates a concise, project-specific DevOps agent that automates infrastructure and CI/CD tasks while preventing accidental modification of application code and avoiding speculative or irrelevant tooling instructions.

Core Features & Use Cases

  • Pre-flight validation: Ensures CLAUDE.md exists and treats an existing .claude/agents/devops.md as an update, failing fast if project settings are missing.
  • Toolchain detection: Scans for Dockerfile, docker-compose, CI workflows, Terraform, Kubernetes manifests, and platform configs to include only detected tools.
  • Safe generation and validation: Produces a 50-80 line .claude/agents/devops.md with valid YAML frontmatter, enforces "never modify application code", checks docs/ before duplicating content, and reports detected tools, line count, and warnings.
  • Use case: Add an infrastructure/CI-CD specialist agent for a repository that uses Docker and GitHub Actions to standardize deployment and debugging workflows.

Quick Start

Create or update the project's DevOps agent focusing only on detected infrastructure tools and prioritize AWS if specified.

Frequently Asked Questions about compiling-devops-agent

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

FAQPage Schema
How do I generate a DevOps agent for Docker and Terraform CI-CD automation?

The Skill creates a 50-80 line .claude/agents/devops.md file containing valid YAML frontmatter and commands strictly for detected infrastructure tools like Docker, Terraform, Kubernetes manifests, or CI workflows.

What do I need to set up before adding an infrastructure specialist agent?

Before adding an infrastructure specialist agent, you need a CLAUDE.md file present in your repository. The generation process fails fast if this project settings file is missing, ensuring proper pre-flight validation before creating the DevOps agent.

Can I update an existing CI-CD specialist agent without overwriting application code?

Yes, you can update an existing CI-CD specialist agent safely because the process treats an existing .claude/agents/devops.md as an update target. It strictly enforces a never-modify-application-code constraint to prevent accidental changes to your source files.

How does toolchain detection work when generating infrastructure automation configs?

Toolchain detection for infrastructure automation configs works by scanning your repository for Dockerfiles, docker-compose files, CI workflows, Terraform files, Kubernetes manifests, and platform configs. The generated agent includes only commands for the specific tools it detects.

What happens if my project has documentation that duplicates the DevOps agent instructions?

If your project has documentation that duplicates DevOps agent instructions, the generator checks the docs/ directory before writing content to avoid duplication. It then reports detected tools, line count, and warnings to ensure a concise 50-80 line output.