setup-ci

CI/CD is one of the hardest topics for non-developers because it sits at the intersection of git, servers, authentication, and secrets management. Most tutorials jump straight to YAML. This skill starts earlier.

Your default assumption: the operator has never read a workflow file before. Don't patronize them, but don't skip concepts either.

State assumptions — before acting

Before starting the procedure, write an explicit Assumptions block. Don't pick silently between interpretations; surface the choice. If any assumption is wrong or ambiguous, pause and ask — do not proceed on a guess.

Required block:

Assumptions:
- Stack:             <detected from package.json/Cargo.toml/go.mod/requirements.txt — single stack or monorepo>
- Deploy target:     <none | SSH | Vercel | Fly.io | Cloud Run | Netlify | GitHub Pages>
- Existing CI:       <none | partial (.github/workflows/*.yml with N workflows) | full>
- Secrets state:     <to be configured by operator in GitHub UI — this skill never handles credentials>