Menu
Deploy Your Project to production safely. Use before any deployment, after code changes, or when asked to push to prod.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Translate git history and orchestrator logs into authentic social content. Use when turning recent technical work into tweets, Dev.to posts, or changelog entries without manual summarisation.
Red team the staging environment with injection attacks, rate limit probes, and auth bypass attempts. Use before major releases or when adding new user-input surfaces.
Facilitate a structured CONVERSATIONAL meeting between department agents via claude-peers — named phases (Diverge, Clarify, Challenge, Build, Stress Test, Converge, Decide) with state machine navigation. Agents push back on each other and build on each other's ideas. Minimum path: Diverge → Challenge → Build → Stress Test. Early exit only after Stress Test. NOT for simple task dispatch (use orchestra-management). NOT for solo research (use rd-architect).
Manage the 6-department orchestra via claude-peers. Use when dispatching tasks, coordinating departments, reviewing results, or shaping department behavior.
Write emails, social posts, and newsletter submissions for Your Project. Use when creating maker outreach, blog content, social media posts, or press pitches.
Research & Development Architect — researches improvements, writes proposals, manages autoresearch loops. Use when hitting a bottleneck, exploring new tech, or running improvement experiments.
| name | deploy-safely |
| description | Deploy Your Project to production safely. Use before any deployment, after code changes, or when asked to push to prod. |
| metadata | {"version":"2.0.0","author":"Master Agent","category":"operations","updated":"2026-03-30T00:00:00.000Z"} |
You are responsible for getting code safely to production on Fly.io.
Check:
git statuspython3 smoke_test.pyCode changes committed, smoke test passing, deploy to Fly.io.
Critical bug found, need to deploy ASAP. Skip non-essential checks but ALWAYS smoke test.
No deploy — just run smoke tests and health checks. Report status.
python3 -c "import ast; ast.parse(open('changed_file.py').read())" for each changed filepython3 smoke_test.py — must be 48/48git add {specific files} — NEVER git add -A or git add .git commit -m "descriptive message"# Preferred (remote build — avoids local disk issues)
~/.fly/bin/flyctl deploy --remote-only
# Fallback (local Docker build)
~/.fly/bin/flyctl deploy --local-only
curl -sL -o /dev/null -w "%{http_code}" https://your-project.fly.dev/health — expect 200git add -f (gitignored)docker system prune -af, retry with --remote-only~/.fly/bin/flyctl logs --no-tail | tail -20--local-only filled local disk during extended sessions — prefer --remote-only