frontend-release
Skill4 starsChanged 21 days agoMITView on GitHub
Verify frontend releases with project-aware build, route smoke checks, assets, i18n, and version validation.
In this repository45 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- a11y-auditorSkill
- api-contract-reviewSkill
- backend-releaseSkill
- bug-diagnosisSkill
- client-copy-reviewSkill
- codebase-designSkill
- code-reviewSkill
- create-issueSkill
- create-prSkill
- create-taskSkill
- dependency-upgradeSkill
- deploy-evidenceSkill
- design-expertSkill
- design-system-docsSkill
- design-system-setupSkill
- domain-modelingSkill
- e2e-verifySkill
- evidence-auditSkill
- feature-discoverySkill
- generate-readmeSkill
- handoffSkill
- implement-taskSkill
- incident-responseSkill
- init-projectSkill
- live-docsSkill
- mcp-debuggingSkill
- memory-curatorSkill
- plan-expertSkill
- planning-featuresSkill
- project-memory-initSkill
- project-memory-refreshSkill
- project-profileSkill
- project-releaseSkill
- proof-runnerSkill
- release-checklistSkill
- researchSkill
- security-hardeningSkill
- security-reviewSkill
- tddSkill
- wiki-forgeSkill
- wiki-initSkill
- wiki-querySkill
- wiki-syncSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Use for Angular, React, Vue, Svelte, static, or SPA frontend releases.
- Distinctive: line 18
Run or list exact checks: install status, lint, typecheck, tests, build.
- Very specific: line 21
Run deploy-evidence before declaring completion.
- Distinctive: line 31
Never mark complete without exact environment smoke evidence.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Frontend Release
Use for Angular, React, Vue, Svelte, static, or SPA frontend releases.
Steps
- Load
project-profilefor app-specific release rules. - Detect framework and package manager from repo files.
- Identify build output policy: committed artifact, CI artifact, or platform build.
- Run or list exact checks: install status, lint, typecheck, tests, build.
- Inspect generated entrypoints and lazy chunks where relevant.
- Smoke public routes and app routes required by the profile.
- Run
deploy-evidencebefore declaring completion.
Required checks to consider
- Version or build identifier where the project has one.
- i18n files when visible text changes.
- Critical routes and auth redirects.
- Console/network errors for browser apps when browser tooling is available.
- Static asset paths and cache-sensitive files.
Never mark complete without exact environment smoke evidence.
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.