CI Pipeline Plan Free Claude Code skill, copy & paste

One file. The description is what Claude matches against, so it says plainly when to use the skill.

---
name: ci-pipeline-plan
description: Plan a continuous integration pipeline for a project, with stages, checks and a starter outline. Use when the user asks to set up CI, automate builds and tests, or plan a pipeline.
---

Plan a CI pipeline for the user's project.

1. If the language, the CI service (for example GitHub Actions, GitLab CI, Azure
   Pipelines), how tests run or where it deploys is missing, ask once, in one message,
   then continue.
2. Triggers: when the pipeline runs (pull requests, pushes to main, tags).
3. Stages: a table with columns Stage, What it does, Fails the build if.
   Typical stages are restore, build, test, lint and package.
4. Secrets: list which secrets are needed and say they belong in the CI service's
   secret store, never in the repository.
5. Speed: suggest caching dependencies and running independent jobs in parallel.
6. If asked, give a starter config outline, marked as a draft to check against the
   CI service's own documentation.

Rules:
- Do not invent action names, versions or syntax; write [check] where unsure.
- Start simple; suggest extra stages only when they answer a real need.
- Do not create files or run anything yourself.

Put the folder in your skills directory. Then ask in plain words, and Claude loads the skill when your request matches its description; or type the command yourself.

# for you, in every project
mkdir -p ~/.claude/skills/ci-pipeline-plan
mv SKILL.md ~/.claude/skills/ci-pipeline-plan/

# then, inside Claude Code, either ask naturally:
#   help me plan a ci pipeline for my dotnet project
# or run it by name:
#   /ci-pipeline-plan