verify-app
Skill1 starsChanged 5 days agoMITView on GitHub
Verify an application change in action before declaring the task done. Use after implementing or fixing UI, layout, styling, routing, client state, or rendered data in web, desktop (macOS/Windows/Linux), mobile, CLI/TUI, or game apps.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- paureis/pau-skillstheir own version, first seen Nov 8, 2026
- joi-fairshare/agentic-workflowtheir own version, first seen Nov 8, 2026
- woodbeary/later-dogtheir own version, first seen Nov 1, 2026
- jthorare/agentic-workflowtheir own version, first seen Oct 25, 2026
- cskwork/skillstheir own version, first seen Oct 9, 2026
- martinappberg/chimaeratheir own version, first seen Sep 28, 2026
Used with
Projects with it also use bughunt.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
avSkillbughunt
Fully autonomous bug hunting pipeline — discover bugs in a scoped area using parallel subagents, independently triage each finding, fix confirmed issues with subagents, then audit all fixes against repo constraints and target platforms. Runs end-to-end without user interaction.
Also in 3 projects that use this
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- martinappberg/chimaera★ 7same name
- cskwork/skills★ 3same name
- joi-fairshare/agentic-workflow★ 3same name
- jthorare/agentic-workflow★ 3same name
- paureis/pau-skills★ 2same name
- woodbeary/later-dog★ 2same 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 repository23 other files it gives its agents.
- AGENTS.mdAGENTS.md
- broSkill
- create-my-skillSkill
- glassmorphismSkill
- swiftui-designSkill
- humanizerSkill
- ponytail-auditSkill
- ponytail-debtSkill
- ponytail-gainSkill
- ponytail-helpSkill
- ponytail-reviewSkill
- ponytailSkill
- clean-up-git-historySkill
- commit-msgSkill
- diagnoseSkill
- fixSkill
- grill-meSkill
- implementSkill
- loopSkill
- subagentsSkill
- update-docsSkill
- sudo-ssh-authSkill
- web-app-secSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
2
Distinctive
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 14
Check every screen, mode, or command that shares the state, data, or components you touched, and the surrounding flows, to catch …
- Distinctive: line 18
If verification finds a problem, fix it and re-verify.
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Verify App
A screenshot shows appearance, not behavior. Before declaring the task complete, confirm the change works in the app.
Steps
- Exercise the changed feature end to end the way a real user would, and confirm behavior, not just appearance. Web: browser tools. Native and desktop (macOS, Windows, Linux): Computer Use or the platform's UI automation and screenshots. Mobile: simulator or emulator. CLI/TUI: run the command with real inputs and check output and exit codes. Games: play the changed path and check the on-screen result.
- Check every screen, mode, or command that shares the state, data, or components you touched, and the surrounding flows, to catch regressions.
- Cover the edge states your change touches: empty, error, and variants such as routes, flags, window sizes, devices, or inputs. If layout or styling changed, check the layouts a real user will see.
- If verification finds a problem, fix it and re-verify. If verification is impossible (no simulator, no access), say so in the report with the reason.
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.