Brandedflow deploy-preflight
Run a pre-deploy safety checklist before pushing code or deploying a service. Covers env vars, breaking changes, rollback plan, and service dependencies. Use before any production deploy.
install
source · Clone the upstream repo
git clone https://github.com/JenCW/brandedflow
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/JenCW/brandedflow "$T" && mkdir -p ~/.claude/skills && cp -r "$T/.claude/skills-library/deploy-preflight" ~/.claude/skills/jencw-brandedflow-deploy-preflight && rm -rf "$T"
manifest:
.claude/skills-library/deploy-preflight/SKILL.mdsource content
Deploy Preflight
When to Use
- Before pushing to production
- Before deploying to Render, Netlify, or Vercel
- Before merging a major PR
- Before running a migration
Checklist
Code Safety
- No hardcoded secrets or API keys in code
- Environment variables documented (all
have correspondingprocess.env.*
entries).env.example - No
with sensitive dataconsole.log - Error handling covers external API failures
- No
blocking the deployTODO: fix this
Breaking Changes
- API contracts unchanged (or versioned)
- Database schema migrations tested
- Dependent services notified if interface changed
- Backwards compatibility confirmed (or cutover planned)
BrandedFlow Service Dependencies
- MCP server (
) — healthy?brandedflow.onrender.com - n8n (
) — healthy?n8n-automation-r6iy.onrender.com - Hub API (
) — healthy?brandedflow-hub-api.onrender.com - Neon PostgreSQL — connection string valid?
- Airtable API keys — valid and scoped?
Rollback Plan
- Can redeploy previous version in < 5 min?
- Database changes reversible?
- Feature flag to disable if needed?
Post-Deploy Verification
- Health check endpoint returns 200
- Key user flow tested end-to-end
- Logs monitored for 10 min post-deploy
Output
Report: ✅ PASS or ❌ FAIL per section. List any blocking issues before deploy proceeds.
End of Task
State: "END-OF-TASK: Directive [N/A]. Self-annealing [N/A]."