verify-frontend-change
Skill0 starsChanged 4 months agoMITView on GitHub
Verify any UI change end-to-end before declaring it done. Trigger whenever a task touches a component, page, button, form control, or any other visible frontend behavior.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- jazzpujols34/claude-skillstheir own version, first seen Oct 13, 2026
- vscarpenter/gsd-task-managertheir own version, first seen Oct 6, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- vscarpenter/gsd-task-manager★ 40same name
- jazzpujols34/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- code-reviewSkill
- test-strategySkill
- adversarial-code-reviewSkill
- avoid-agentic-pitfallsSkill
- bug-triage-runbook-templateSkill
- changelog-from-commitsSkill
- checkout-verifier-templateSkill
- choose-your-loopSkill
- commit-message-qualitySkill
- dependency-update-checkSkill
- env-doctorSkill
- library-reference-templateSkill
- new-feature-scaffoldSkill
- pr-description-generatorSkill
- python-to-ts-migration-templateSkill
- readme-generatorSkill
- safe-refactorSkill
- systematic-debuggingSkill
- verify-code-changeSkill
- verify-form-changeSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Never report a UI change as complete based on a successful edit alone.
- Distinctive: line 10
Verify it the way a human reviewer would:
- Distinctive: line 12
Start the dev server and open the edited page in the browser.
- Distinctive: line 16
Check the browser console: zero new errors or warnings.
- Distinctive: line 17
Use the Chrome Devtools MCP, run a performance trace and audit Core Web Vitals.
- Distinctive: line 20
If any step fails, fix the issue and rerun from step 1 — do not hand back partially verified work.
≈ “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
<!-- Source : docs/guide-complet.md, Partie 1.2 (Boucle turn-based) -->Verifying frontend changes
Never report a UI change as complete based on a successful edit alone. Verify it the way a human reviewer would:
- Start the dev server and open the edited page in the browser.
- Interact with the change directly. For a new control (button, input, toggle): click it, confirm the expected state change, and screenshot before/after.
- Check the browser console: zero new errors or warnings.
- Use the Chrome Devtools MCP, run a performance trace and audit Core Web Vitals.
If any step fails, fix the issue and rerun from step 1 — do not hand back partially verified work.
Gotchas
- Attendre un état observable (message de confirmation affiché, spinner disparu) et jamais un délai fixe : un délai fixe passe en local et échoue en CI ou sur une machine plus lente.
- Ajouter une ligne à cette section à chaque fois que Claude rate un
cas particulier malgré ce skill, plutôt que de corriger uniquement le
cas isolé (voir
docs/guide-complet.md, Partie 1.6).
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.