staging-deploy
Deploying, shipping, or pushing code to staging — runs tests, build, image push, staging migration, deploy, and smoke-check in order, with the safeguard that keeps migrations off prod.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- staging-deploy
- description
- Deploying, shipping, or pushing code to staging — runs tests, build, image push, staging migration, deploy, and smoke-check in order, with the safeguard that keeps migrations off prod.
02 资源文件 2
- 参考文档grading.json1.0 KB
- 参考文档meta.json197 B
03 SKILL.md 正文
Deploy to staging by running this sequence in order. Each step depends on the one before it succeeding — do not skip or reorder.
- Test —
pnpm test. Done when the command exits 0. A failing suite stops the deploy here. - Build —
pnpm build. Done when the command exits 0. - Push image —
make docker-push TAG=staging-<git-sha>, where<git-sha>is the current commit's short SHA (git rev-parse --short HEAD). Done when the push exits 0. Note the tag — step 6 checks against it. - Migrate —
pnpm db:migrate:staging. Target the staging DB only: the.envfile holds the staging and prod URLs side by side, so confirm the command is reading the staging one before running it. Done when the migration exits 0. - Deploy —
make deploy-staging. Done when the command exits 0. - Smoke-check — request
https://staging.acme.dev/healthzand confirm both: the response is200, and its reported sha matches the<git-sha>from step 3. Done only when both hold — a200alone is not enough.
If the smoke-check fails, roll back immediately: make rollback-staging. Do not patch forward on a failed staging deploy.
04 同仓库更多 Skills
review-adversarial-first
Operator-invoked adversarial review: 3 refute-by-default lenses plus a deterministic judge against a PR, branch, or path, then a decision on whether /ce-code-review's topic fan-out runs. Off the default merge path since the 2026-10-17 merge-and-end ruling; run only when asked for by name.
memory-mine
Run one deterministic, budgeted directed-capture batch for an explicit Claude Code project store. Use manual workspace mode only when cross-agent cass sessions are intentionally in scope.
papers
Search preprints from arXiv, bioRxiv, and medRxiv without API keys. Supports search, lookup, extraction, citations, enrichment, and paper downloads that bundle PDFs plus linked GitHub code.
papers
Search preprints from arXiv, bioRxiv, and medRxiv without API keys. Supports search, lookup, extraction, citations, enrichment, and paper downloads that bundle PDFs plus linked GitHub code.
wsl-cdp
Drive the user's real, logged-in Windows browser (Chrome, Edge, or Brave) from a Claude Code session running inside WSL2, over the Chrome DevTools Protocol - read authenticated dashboards and consoles, take real screenshots, open and read pages with the user's sessions. Use when a task needs the user's existing web logins and the session runs in WSL2, where the Claude in Chrome extension cannot work. Not for native-Windows or macOS Claude Code (use the official Claude in Chrome extension), not for anonymous scraping or CI (use headless Playwright inside WSL), not for getting past login walls (those are handed to the human).
token-eater
[BETA] Spend a subscription's idle, about-to-expire credits on safe, machine-verified cleanup. You pick the service (Grok / Codex / Claude) and a token-heavy maintenance skill (de-monolithize, de-slop, simplify, dead-code); that service runs the whole skill -> gate -> self-review -> draft-PR loop on its own credits, in an isolated worktree. token-eater verifies the gate and never merges. Manual invocation only during beta.