denchhq Land and Deploy — From Approved to Verified
Takes over where ship left off. Merge, deploy, verify.
Related skills: ship | canary | qa
Step 1: Pre-Merge Checks
gh pr checks
gh pr view --json reviewDecision -q .reviewDecision
- All CI checks must pass
- PR must be approved (or the user explicitly overrides)
Step 2: Merge
gh pr merge --squash --delete-branch
Use squash merge by default (clean history). If the user prefers merge commits, honor that.
Step 3: Wait for Deploy
Monitor the deployment:
- Check CI/CD status after merge
- Wait for deploy to complete (poll deployment status)
- If deploy fails, alert the user immediately
Step 4: Production Verification
After deploy completes:
- Navigate to the production URL
- Verify the shipped feature works
- Check for console errors
- Check for network errors
- Screenshot key pages
Step 5: Post-Deploy
DEPLOY REPORT
═══════════════════════════════════════
PR: #123 (merged)
Deploy status: SUCCESS
Production URL: https://app.example.com
Verification: PASS
═══════════════════════════════════════
If something breaks, offer to revert:
gh pr create --title "Revert: ..." --body "Reverting PR #123 due to ..."
For extended monitoring, use canary.