dk-release - SKILL.md Agent Skill

name: dk-release description: DK Agency release gate — run before merging and after merging to confirm a change is actually live on dkagency.com.tr, not just merged. Prevents the "merge etdim amma çıxmadı" deploy gap. when_to_use: finishing a task, preparing to merge, or confirming a deploy reached prod. disable-model-invocation: true

Release gate (DK Agency)

Deploy target: Hostinger auto-deploy from main. See dk-deploy-reality for the why.

A. Before merge (Definition of Done — every item, raw output)

NEXT_TURBOPACK_EXPERIMENTAL_USE_SYSTEM_TLS_CERTS=1 npm run build → 0 TS error
npm run lint → 0 new error
npm run verify:staged → pass
Playwright @smoke executed (not just written)
Route HEAD → 200/307 on the prefix-less URL (404/500 = fail)
Gated API POST → 401 without auth (gating proof)
New component: grep hardcoded AZ/TR → 0 hits
docs/CHANGELOG.md + docs/DEVLOG.md updated
npm run dk:validate → 8/8 PASS visible in PR/commit (skip only with stated technical reason)
Each task = branch + PR + dk-validator. Never --no-verify.

B. After merge — prove it's LIVE (do not stop at "merged")

Merging ≠ live. When the user expects the change on prod:

Confirm PR merged to main.
Hostinger redeployed? build log ✓ Compiled successfully (not Killed/OOM).
Node app restarted (most common miss → stale .next → old behavior / 404 / 503).
Verify the live URL (prefix-less) returns the new behavior; hard-refresh / incognito.

If a route 404s or the site 503s after deploy, switch to the dk-deploy-reality skill and diagnose merge→build→restart→cache in that order before touching code.