← ShipFrameCONTENT HISTORY

Update to ShipFrame

Snapshot Sep 30, 2026 · 23:14 UTC · version 0.4.2

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "name": "frontend-release",
  "description": "Verify frontend releases with project-aware build, route smoke checks, assets, i18n, and version validation.",
  "included_files": [],
  "skill_md_contents": "---\nname: frontend-release\ndescription: Verify frontend releases with project-aware build, route smoke checks, assets, i18n, and version validation.\nallowed-tools: Read Glob Grep Bash\nargument-hint: '[--app <name>] [--environment <name>]'\neffort: medium\n---\n\n# Frontend Release\n\nUse for Angular, React, Vue, Svelte, static, or SPA frontend releases.\n\n## Steps\n\n1. Load `project-profile` for app-specific release rules.\n2. Detect framework and package manager from repo files.\n3. Identify build output policy: committed artifact, CI artifact, or platform build.\n4. Run or list exact checks: install status, lint, typecheck, tests, build.\n5. Inspect generated entrypoints and lazy chunks where relevant.\n6. Smoke public routes and app routes required by the profile.\n7. Run `deploy-evidence` before declaring completion.\n\n## Required checks to consider\n\n- Version or build identifier where the project has one.\n- i18n files when visible text changes.\n- Critical routes and auth redirects.\n- Console/network errors for browser apps when browser tooling is available.\n- Static asset paths and cache-sensitive files.\n\nNever mark complete without exact environment smoke evidence.\n"
}

SHA-256: 0e058dbc64c6746b43b77038d9bc25895b2c8f05cc01710a0dfafb349632af72