Menu
How to set up and maintain CI/CD per stack. GitHub Actions patterns, testing configurations, deployment scripts.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Complete reference for the factory CLI — all commands, arguments, options, and usage. Use when an agent needs to invoke factory commands, check correct syntax, or understand available options.
When and how to write a human-action-needed entry to memory/{agent}/needs.md. Agents write these entries when they hit blockers that only a human can resolve.
When you encounter a failure, correction, or new pattern, write a learning and optionally propose a skill.
How the factory workspace is organized and what each directory means.
What to examine during a reflection pass and how to write observations to memory/{agent}/needs.md.
When and how to write scenario holdouts for factory verification.
| name | ci-cd |
| description | How to set up and maintain CI/CD per stack. GitHub Actions patterns, testing configurations, deployment scripts. |
When Builder completes a new project, Operator sets up CI. Standard checklist:
.github/workflows/ci.yml with the appropriate test runnerpush to main and on pull requestsPython
- uses: actions/setup-python@v4
with: { python-version: "3.11" }
- run: pip install -e ".[dev]"
- run: pytest
Node / TypeScript
- uses: actions/setup-node@v4
with: { node-version: "20" }
- run: npm ci
- run: npm test
On each heartbeat: check main branch CI (gh run list --branch main), action version
pins, and test command accuracy. A failing main branch is the highest priority —
address before any other operational work.
Deployment scripts live in projects/{project-name}/.factory/deploy.sh or as a
GitHub Actions workflow. Do not invoke deployments without explicit human authorization.
Confirm target environment, authentication method, and rollback procedure before writing.