Deployment Pipeline Hardening skill for Claude and Codex

Deployment Pipeline Hardening as an AI skill. It asks for Pipeline config, Hosting target, CI system and 3 more, then does the rest. Free to install in Claude…

Install it once and Claude or Codex runs it for you. When your request matches, your AI loads the skill, asks for anything it is missing, and works through the template itself. Prefer to fill it in by hand? See the full prompt template.

Download the skill (.zip) · View SKILL.md

When it is used

Use when a CI/CD pipeline needs a review of its gates, health checks, rollback path, and secret handling before more traffic depends on it. Do not use for writing a pipeline from scratch or choosing a hosting provider. Related topics: devops, coding.

What it will ask you for

• Pipeline config (longer free text)
• Hosting target (free text, e.g. "Kubernetes or Cloud Run")
• CI system (choose one: GitHub Actions, GitLab CI, CircleCI, Jenkins, Other)
• Release frequency (choose one: Many per day, Daily, Weekly, Rarely)
• Environments (free text, e.g. "staging and production")
• Concerns (choose any: Rollback, Health checks, Secrets, Approvals, Caching, Supply chain)

How it works

1. Trace one commit from push to production and list each stage with what it proves and what a failure does.
2. Find missing gates, such as tests that do not block deploys or a release with no post-deploy smoke check.
3. Confirm a one-step rollback exists and that database changes are compatible with both old and new code.
4. Audit secret handling and third-party step pinning, including exposure to pull requests from forks.
5. Return findings by risk, corrected snippets for the top three, and a short rollback runbook.

What you get

Findings ordered by risk, corrected pipeline snippets for the top three, and a rollback runbook of no more than ten steps.

What it watches out for

• Counting a green build as proof of safety when nothing checks the deployed service afterwards.
• Rebuilding the artifact per environment, so production runs code that staging never tested.
• Printing environment variables in a debug step and leaking secrets into public build logs.

How to install

Claude.ai and the Claude desktop app

1. Download the skill .zip.
2. Open Settings, then Capabilities, and find Skills.
3. Choose Upload skill and select the .zip.
4. Ask Claude for help with the task. It loads the skill when your request matches.

Claude Code

1. Download the skill .zip.
2. Unzip it into ~/.claude/skills/ (or .claude/skills/ inside a project).
3. Start a new session. Claude Code loads the skill when your request matches.

Codex

1. Download the skill .zip.
2. Unzip it into ~/.agents/skills/ (or .agents/skills/ inside a project).
3. Codex picks it up on its own. Type $ and the skill name to use it, or just ask for the task.

Cursor

1. Download the Cursor rule (.mdc).
2. Save it in .cursor/rules/ inside your project.
3. Cursor's agent applies the rule when your request matches its description.

AGENTS.md (Codex, Cursor, and other coding agents)

1. Copy the AGENTS.md section.
2. Paste it into AGENTS.md at the root of your repository, creating the file if needed.
3. Coding agents that read AGENTS.md follow it when your request fits.