shadow-release
Skill1 starsChanged yesterdayMITView on GitHub
Production Release & Rollback Management. Use when preparing production deployments, SemVer changelogs, pre-flight checklists, migration backward-compatibility gates, feature flags, or rollback runbooks.
- Reads credentials
In this repository51 other files it gives its agents.
- antislop-codeSkill
- antislop-copywritingSkill
- antislop-humanSkill
- antislop-layoutmobileSkill
- antislopSkill
- antislop-uiSkill
- context7Skill
- handoffSkill
- shadow-accessibilitySkill
- shadow-apiSkill
- shadow-architectSkill
- shadow-authSkill
- shadow-bootstrapSkill
- shadow-browserSkill
- shadow-cacheSkill
- shadow-compatSkill
- shadow-concurrencySkill
- shadow-dataSkill
- shadow-dbSkill
- shadow-debugSkill
- shadow-designSkill
- shadow-discoverySkill
- shadow-docSkill
- shadow-domainSkill
- shadow-eaSkill
- shadow-evalSkill
- shadow-finopsSkill
- shadow-gitSkill
- shadow-grcSkill
- shadow-handoverSkill
- shadow-integrateSkill
- shadow-maintainSkill
- shadow-mobileSkill
- shadow-modernizeSkill
- shadow-monarchSkill
- shadow-observeSkill
- shadow-opsSkill
- shadow-perfSkill
- shadow-planSkill
- shadow-pmoSkill
- shadow-presalesSkill
- shadow-privacySkill
- shadow-qualitySkill
- shadow-realtimeSkill
- shadow-refactorSkill
- shadow-resilienceSkill
- shadow-searchSkill
- shadow-secSkill
- shadow-supplychainSkill
- shadow-testSkill
- shadow-uatSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill before every Staging or Production deployment to guarantee that a release is traceable, backward-compatible, backed up, and …
- Very specific: line 34
Before deploying to Production, verify all 8 release gates (treat any missing required artifact as an immediate BLOCKED status — never …
- Very specific: line 49
Check /healthz and /readyz return 200 OK.
- Very specific: line 50
Check container/service logs (docker compose logs --tail=50 / journalctl) for zero startup errors.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Shadow Release (/shadow-release) — Release Readiness Gate, Versioning & Rollback Verification
Use this skill before every Staging or Production deployment to guarantee that a release is traceable, backward-compatible, backed up, and instantly reversible if an incident occurs.
1. Semantic Versioning & Release Manifest (SemVer 2.0.0)
Determine version bump (MAJOR.MINOR.PATCH) from the verified commit history since the last tag:
MAJOR(v2.0.0): Breaking API/webhook contract changes or incompatible architecture shifts (requires/shadow-compatmigration plan).MINOR(v1.3.0): Backward-compatible new features, endpoints, or additive DB migrations (feat:).PATCH(v1.2.1): Backward-compatible bug fixes, security patches, or performance tuning (fix:,perf:,sec:).
Release Notes / CHANGELOG.md Structure
Group all user- and operator-relevant changes under:
- Breaking Changes & Required Action (
ENVvars, migrations, config updates) - Added (
Features) - Fixed (
Bug Fixes) - Security & Performance
- Rollback Instructions (Exact git tag / image digest & command)
2. Pre-Flight Release Readiness Checklist (Gate 6)
[!CAUTION] Read-Only Default Rule:
/shadow-releaseprepares and audits the release checklist first. Never execute a live production deployment or production DB migration without explicit confirmation from the Monarch.
Before deploying to Production, verify all 8 release gates (treat any missing required artifact as an immediate BLOCKED status — never "warn and ship"):
- Gate 1 — Quality & Tests: Lint, strict typecheck, and automated test suite (
/shadow-test+/shadow-quality) pass on the exact release commit SHA. - Gate 2 — Security Audit:
/shadow-secreports zero hardcoded secrets, zero reachable critical vulnerabilities, and auth/tenant guards verified. - Gate 3 — Pre-UAT Performance & Staging UAT:
/shadow-perfbaseline and/shadow-uatStaging verification passed. - Gate 4 — Pre-Deploy Database Backup: Fresh production database backup (
pg_dump/mysqldump) created and checksum-verified (/shadow-ops). - Gate 5 — Migration-Before-Code Ordering (
/shadow-data): Expand-only migrations execute and verify cleanly before deploying new application containers so rolling back code remains safe; defer destructive Contract/cleanup migrations until old instances finish draining. - Gate 6 — Environment Parity: Any new
.envkeys added in.env.exampleare confirmed present in the target server/secret manager. - Gate 7 — Rollback Command Ready: Previous working image tag / commit SHA recorded (
PREV_TAG) with a 1-command rollback script tested. - Gate 8 — Supply-Chain SBOM & Provenance (
/shadow-supplychain): Verify generated CycloneDX/SPDX SBOM, lockfile integrity, immutable container image digest pinning (zero:latest/ floating action tags), and build provenance attestation (supplychain_sbom_gate.py). Missing SBOM or provenance artifact blocks release (BLOCKED).
3. Post-Deploy Production Smoke Verification
Immediately after deployment finishes (within < 2 minutes):
- Check
/healthzand/readyzreturn200 OK. - Check container/service logs (
docker compose logs --tail=50/journalctl) for zero startup errors. - Execute read-only smoke checks on critical public/authenticated routes (
/shadow-api//shadow-browser). - Monitor error rate and
p95latency for 15 minutes (/shadow-observe). If 5xx rate spikes above threshold, execute the rollback command immediately. - Execution Approval Boundary (
L0vsL4): Preparing release checklists, SBOM verification, and SemVer changelogs isL0_READ_ONLY. Executing production deploys, live migrations, or tag pushes isL4: HIGH_IMPACTrequiring explicit 7-part Monarch approval and rollback verification (shadow-monarch/scripts/execution_approval_gate.py).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

