Menu
Deploy a reviewed service with explicit confirmation and verification.
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
GitHub issue, pull request, CI, release, and code review workflow for Product Factory OS projects. Use when work involves GitHub Issues, PR summaries, review comments, failing GitHub Actions, release branches, changelogs, or publishing project state to GitHub.
Generate infrastructure-as-code and deployment configuration.
Safely apply database or data migrations with backup and rollback notes.
Security-audit v2 workflow for application, repository, scoped path, PR, branch, or working-tree security review. Use for security audit, OWASP, secrets, threat model, attack path, Codex Security diff scan, release security gate, or security_change evidence requests.
Improve SEO effectiveness for products, landing pages, docs, and content by auditing technical SEO, search intent, metadata, structured data, content gaps, and measurement loops. Use for SEO audit, organic traffic, indexing, sitemap, robots.txt, schema, canonical, meta tags, Search Console, and content optimization work.
Save PFO work context, state, decisions, blockers, and next steps for continuity.
| name | deploy |
| description | Deploy a reviewed service with explicit confirmation and verification. |
| argument-hint | service name, target environment, or release |
| license | MIT |
| metadata | {"category":"operations","tags":["deploy","release","production"],"effort":"high","side_effect":"production-impact","explicit_invocation":true,"skill_version":1,"prompt_version":"pfo-deploy-v1","eval_dataset":"tests/eval-datasets/deploy.json"} |
Deploy only after explicit confirmation.
Use docs/rubrics/production.md for production readiness preflight.
Check:
BLOCKED/browser-check failures and include target, engine, flow, and screenshot/log evidence when applicable/github-workflow is in scopeBefore any real deployment command, ask:
Confirm deployment target and impact: deploy <service> to <environment>? This may restart services.
Proceed only after explicit confirmation.
/tool-sync or /github-workflow when external release status must be updated.At minimum:
Every deploy report must include one:
Before final output, verify:
/session-save after a production deploy attempt.