chore: mark 3 TODOs completed, bump v0.7.0, update CHANGELOG

Superseded by /land-and-deploy:
- /merge skill — review-gated PR merge
- Deploy-verify skill
- Post-deploy verification (ship + browse)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Garry Tan
2026-03-18 06:07:11 -07:00
parent 3c3be2dc35
commit c46ada1594
3 changed files with 23 additions and 31 deletions
+16
View File
@@ -1,5 +1,21 @@
# Changelog
## [0.7.0.0] - 2026-03-18
### Added
- **`/land-and-deploy` — the missing piece after `/ship`.** Merges your PR, waits for CI and deploy workflows, then runs a canary health check on production. Auto-detects merge queues, deploy platforms (Vercel, Netlify, Fly.io, GitHub Actions), and production URLs. Offers one-click revert if something breaks. Timing data (CI wait, queue, deploy, canary) logged for retrospectives. The workflow is now: `/review``/ship``/land-and-deploy`.
- **`/canary` — standalone post-deploy monitoring.** Watches production for 10 minutes after a deploy using the browse daemon. Takes periodic screenshots, detects new console errors, flags performance regressions (>2x baseline). Run `--baseline` before deploying to capture the "before" state. Alerts on *changes*, not absolutes — 3 pre-existing errors is fine, 1 new error is an alert.
- **`/benchmark` — performance regression detection.** Collects real Web Vitals (TTFB, FCP, LCP), bundle sizes, and request counts via `performance.getEntries()` through the browse daemon. Compares against saved baselines with configurable thresholds. Trend analysis across historical runs. Performance budgets with letter grades.
- **Performance & Bundle Impact review category.** `/review` and `/ship` now catch heavy dependency additions (moment.js → date-fns), missing lazy loading, synchronous scripts, CSS @import blocking, fetch waterfalls, and tree-shaking breaks. Added to `review/checklist.md` as an INFORMATIONAL category.
- **Deploy bootstrap auto-detection.** First time you run `/land-and-deploy`, it scans your repo for deploy platforms, production URLs, and merge method preferences. Saves results to CLAUDE.md so future runs skip detection. Same pattern as test bootstrap.
- **"Deployed" row in Review Readiness Dashboard.** After `/land-and-deploy` runs, the dashboard shows deploy status (HEALTHY/REVERTED/ISSUES) alongside Eng, CEO, and Design review status.
### For contributors
- Incorporated canary monitoring and benchmark patterns from community PR #151 (HMAKT99).
- 3 new skills registered across gen-skill-docs.ts, skill-check.ts, skill-validation, and gen-skill-docs tests.
## [0.6.4.0] - 2026-03-17
### Added
+6 -30
View File
@@ -161,17 +161,6 @@
**Priority:** P2
**Depends on:** None
### Post-deploy verification (ship + browse)
**What:** After push, browse staging/preview URL, screenshot key pages, check console for JS errors, compare staging vs prod via snapshot diff. Include verification screenshots in PR body. STOP if critical errors found.
**Why:** Catch deployment-time regressions (JS errors, broken layouts) before merge.
**Context:** Requires S3 upload infrastructure for PR screenshots. Pairs with visual PR annotations.
**Effort:** L
**Priority:** P2
**Depends on:** /setup-gstack-upload, visual PR annotations
### Visual verification with screenshots in PR body
@@ -332,14 +321,6 @@
**Priority:** P3
**Depends on:** Video recording
### Deploy-verify skill
**What:** Lightweight post-deploy smoke test: hit key URLs, verify 200s, screenshot critical pages, console error check, compare against baseline snapshots. Pass/fail with evidence.
**Why:** Fast post-deploy confidence check, separate from full QA.
**Effort:** M
**Priority:** P2
### GitHub Actions eval upload
@@ -456,17 +437,6 @@ Shipped as `/design-consultation` on garrytan/design branch. Renamed from `/setu
**Priority:** P3
**Depends on:** gstack-diff-scope (shipped)
### /merge skill — review-gated PR merge
**What:** Create a `/merge` skill that merges an approved PR, but first checks the Review Readiness Dashboard and runs `/review` (Fix-First) if code review hasn't been done. Separates "ship" (create PR) from "merge" (land it).
**Why:** Currently `/review` runs inside `/ship` Step 3.5 but isn't tracked as a gate. A `/merge` skill ensures code review always happens before landing, and enables workflows where someone else reviews the PR first.
**Context:** `/ship` creates the PR. `/merge` would: check dashboard → run `/review` if needed → `gh pr merge`. This is where code review tracking belongs — at merge time, not at plan time.
**Effort:** M
**Priority:** P2
**Depends on:** Ship Confidence Dashboard (shipped)
## Completeness
@@ -484,6 +454,12 @@ Shipped as `/design-consultation` on garrytan/design branch. Renamed from `/setu
## Completed
### Deploy pipeline (v0.7.0)
- /merge skill — review-gated PR merge → superseded by /land-and-deploy
- Deploy-verify skill → superseded by /land-and-deploy canary verification
- Post-deploy verification (ship + browse) → superseded by /land-and-deploy
**Completed:** v0.7.0
### Phase 1: Foundations (v0.2.0)
- Rename to gstack
- Restructure to monorepo layout
+1 -1
View File
@@ -1 +1 @@
0.6.4.0
0.7.0.0