deploy-pr

Deploy PR

Deploys a merged pull request to the target environment, runs smoke tests to verify the deployment, and confirms a rollback plan exists. Bridges the gap between merging code and having it running in production.

Prerequisites

• Apply the shared SDLC conventions in skills/sdlc/references/shared.md.
• If no argument is provided, target the pull request from $PR_NUMBER (and $REPO).
• gh CLI authenticated with write access to the target repository
• A merged PR number or merge SHA provided as $1
• Deployment tooling available (CI/CD pipeline, container registry, or manual deployment scripts)
• Read any files present under .sdlc/context/ for project-level context, especially architecture.md for deployment topology

Workflow

Fetch merged PR details ($1)
        |
        v
  Identify target environment
        |
        v
  Confirm rollback plan exists
     /         \
   Yes          No
    |            |
    v            v
  Execute     Document rollback
  deployment  procedure first,
    |         then proceed
    v
  Run smoke tests
     /         \
   Pass         Fail
    |            |
    v            v
  Verify      Execute rollback
  health      Report failure
    |            |
    v            v
  Report      Stop, investigate
  success

Steps

1. Fetch the merged PR details:

   gh pr view $1 --json title,body,mergeCommit,headRefName,closingIssuesReferences
   

2. Identify the target environment(s) from the PR labels, branch name, or project configuration. Common targets:

   • staging for non-production validation
   • production for user-facing releases
   • Feature-specific environments (e.g., preview, canary) If uncertain, ask the user which environment to deploy to.

3. Check for a rollback plan. Look for:

   • A documented rollback procedure in the PR description or .sdlc/ artifacts
   • Previous deployment version or tag to roll back to
   • Database migration rollback if applicable If no rollback plan exists, document one before proceeding.