deploy-flow

Deploy code to production via feature-branch, test, staging, PR, and merge workflow.

1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/kennyolofsson23-netizen/claude-code-config --skill deploy-flow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy-flow
Source: https://github.com/kennyolofsson23-netizen/claude-code-config/tree/main/skills/deploy-flow
Command: npx skills add https://github.com/kennyolofsson23-netizen/claude-code-config --skill deploy-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents risky, untested code from reaching production by enforcing a deterministic feature-branch workflow with local and CI validation and staging verification so teams don't ship broken releases or bypass tests.

Core Features & Use Cases

  • Structured Feature Branch Workflow: guidance for creating focused branches, conventional commits, and selective staging of changes.
  • Mandatory Test & Staging Gates: requires running all unit, integration, linting, and E2E suites locally and in CI, plus Playwright verification against preview or staging URLs before merging.
  • PR, Merge, and Rollback Playbook: templates for PR bodies, CI gating rules, post-deploy smoke checks, and a safe emergency rollback procedure.
  • Use Case: shipping a bug fix to payments by running full test suites locally, pushing a feature branch, validating CI and staging E2E, opening a detailed PR, and merging only after all checks pass.

Quick Start

Deploy the current feature branch to production by running all local tests, pushing the branch, verifying CI and staging E2E, creating a PR with a clear test plan, and merging only when all checks are green.

Frequently Asked Questions about deploy-flow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy a feature branch to production safely?

A safe production deploy requires running all local tests, pushing a feature branch, validating CI and staging E2E checks, opening a PR, and merging only when all gates pass.

What is a feature-branch to staging to production workflow?

It is a deterministic release process that mandates local and CI test validation, Playwright E2E verification against staging, and PR merge gating on green checks before code reaches production.

How do I run Playwright E2E tests against a staging environment before merging?

You validate Playwright E2E tests against preview or staging URLs during the feature branch workflow, ensuring all integration checks pass before opening a PR for production merge.

Does my CI pipeline need specific gating rules for production deployments?

Yes, CI pipelines need gating rules that block PR merges until all unit, integration, linting, and Playwright E2E test suites return green checks, preventing untested code from reaching production.

What is the best way to rollback a production deployment in an emergency?

The best way to rollback a production deployment in an emergency is to follow a structured playbook that provides safe Git-based recovery instructions for reversing a broken release.