← ShipFrameCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to ShipFrame
Snapshot Sep 30, 2026 · 23:14 UTC · version 0.4.2
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"name": "backend-release",
"description": "Verify backend/API releases with tests, migrations, queues, integrations, and endpoint smoke checks.",
"included_files": [],
"skill_md_contents": "---\nname: backend-release\ndescription: Verify backend/API releases with tests, migrations, queues, integrations, and endpoint smoke checks.\nallowed-tools: Read Glob Grep Bash\nargument-hint: '[--app <name>] [--environment <name>]'\neffort: medium\n---\n\n# Backend Release\n\nUse for Laravel, Node, Python, Rails, Go, or other backend/API releases.\n\n## Steps\n\n1. Load `project-profile` for app-specific release rules.\n2. Detect framework, package manager, and runtime.\n3. Identify migrations, queues, scheduled jobs, webhooks, and external integrations affected by the diff.\n4. Run or list exact checks: dependency validation, lint/static analysis, tests, build/compile.\n5. Check required env/config changes are documented and not committed as secrets.\n6. Smoke health endpoints and affected API routes in the intended environment.\n7. Run `deploy-evidence` before declaring completion.\n\nNever mark complete from a green CI job alone; smoke the intended runtime environment.\n"
}SHA-256: 8e76ac68dba00b4341488260158f2b3db5f9eb64156632564d6051b73c76f54e