{"id":18353,"plugin_id":"plugins_6a88e6256bb48191a343d39dace5e05c","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:14:47.449Z","digest":"0e058dbc64c6746b43b77038d9bc25895b2c8f05cc01710a0dfafb349632af72","against":null,"payload":{"description":"Verify frontend releases with project-aware build, route smoke checks, assets, i18n, and version validation.","included_files":[],"name":"frontend-release","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"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}