automation

Builds and maintains CI/CD pipelines, Docker configurations, and infrastructure-as-code through a structured git worktree workflow.

Updated May 2, 2026
One-click install
npx skills add https://github.com/whinchman/midi-man-mk3 --skill automation-whinchman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: automation
Source: https://github.com/whinchman/midi-man-mk3/tree/main/.claude/skills/automation
Command: npx skills add https://github.com/whinchman/midi-man-mk3 --skill automation-whinchman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams need consistent, version-controlled infrastructure and deployment automation, but building CI/CD pipelines, Dockerfiles, and deployment configs by hand is error-prone and often bypasses review processes. This Skill acts as an Automation Engineer agent that audits existing infrastructure, plans changes, and implements them safely through feature branches and pull requests. ## Core Features & Use Cases - CI/CD Pipeline Construction: Creates GitHub Actions workflows with lint, test, build, and deploy stages, caching strategies, and matrix builds. - Container and Build System Management: Optimizes Dockerfiles with multi-stage builds, defines docker-compose services, and maintains build scripts and dependency lock files. - Safe Change Workflow: Enforces worktree-based development, task tracking via .workflow/tasks/, and pull-request-only delivery with no direct pushes to the default branch. - Use Case: A repository needs automated testing on every push. The agent audits existing workflows, writes an infrastructure plan, creates a feature branch in a git worktree, adds a GitHub Actions pipeline, validates the YAML, and opens a PR for review. ## Quick Start Ask the automation agent to set up a CI pipeline that lints, tests, and builds this repository on every pull request.

Frequently Asked Questions about automation

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

FAQPage Schema
How do I set up a CI/CD pipeline for my repository?▼

The agent audits existing pipelines in .github/workflows/ or similar locations, writes an infrastructure plan, then implements stages for lint, test, build, and deploy in a dedicated git worktree. Changes are delivered through a pull request, never pushed directly to the default branch.

How to optimize a Dockerfile for CI builds?▼

The agent applies layer caching, multi-stage builds, and minimal base images to reduce build time and image size. It also configures health checks, resource limits, and image tagging for registry publishing.

Can this agent modify application code or business logic?▼

No. The agent works exclusively on infrastructure, build tooling, and automation. Application logic and business code are explicitly out of scope per its hard rules.

Does the automation agent push directly to the main branch?▼

No. All changes go through a feature branch in a git worktree and are delivered via a pull request. Direct pushes or merges to the default branch are prohibited without exception.

What happens if no task file exists for the automation work?▼

The agent falls back to reading .workflow/TODO.md and picks the next unchecked item involving infrastructure or automation. It then plans, implements, validates, and opens a pull request for that work.