init-verify
Skill234 starsChanged 3 months agoMITView on GitHub
TEMPLATE-ONLY - verify changes against a fully running stack by instantiating the template, checking in the browser, then reverting every init artifact. Use whenever a change needs visual or runtime verification in the real app. Removed by init.sh, do not reference from skills that survive init.
- Deletes or force-pushes
In this repository29 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- add-aspire-depSkill
- add-background-jobSkill
- add-ci-areaSkill
- add-email-templateSkill
- add-env-varSkill
- add-options-classSkill
- add-permissionSkill
- add-rate-limitSkill
- address-reviewSkill
- add-testSkill
- backend-conventionsSkill
- create-issueSkill
- create-prSkill
- create-releaseSkill
- frontend-conventionsSkill
- gen-typesSkill
- infra-conventionsSkill
- manage-file-storageSkill
- new-endpointSkill
- new-entitySkill
- new-featureSkill
- new-pageSkill
- polish-uiSkill
- review-dependabotSkill
- review-designSkill
- review-prSkill
- security-conventionsSkill
- verifySkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 0 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 5
Verify template changes in a real running app.
- Very specific: line 7
When polishing UI in the template, run /polish-ui step 5 (browser verification) inside this loop.
- Very specific: line 20
Delete untracked init artifacts: verify git ls-files --others --exclude-standard lists ONLY instantiation files, then remove them (the …
- Very specific: line 21
Delete gitignored leftovers too: the instantiation's bin/obj output is invisible to the untracked listing.
- Very specific: line 22
Remove the Docker containers/volumes created since the snapshot (Aspire volumes are named <name>-db-data, <name>-storage-data).
- Very specific: line 27
Commit the meaningful screenshots under docs/sessions/assets/<date>-<topic>/ and embed them in the PR description with SHA-pinned raw URLs …
≈ “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
Verify template changes in a real running app. The template's placeholder form (MyProject) cannot run the full stack; a throwaway instantiation can. Nothing from the instantiation may leak into commits.
When polishing UI in the template, run /polish-ui step 5 (browser verification) inside this loop.
The loop
- Commit first: the real (pre-init, template-form) changes must be committed before anything else - the revert below destroys uncommitted work. Capture the SHA:
PRE_INIT_SHA=$(git rev-parse HEAD). - Snapshot Docker: note existing containers/volumes (
docker ps -aq,docker volume ls -q) so cleanup removes only what this run creates. - Instantiate:
./init.sh --name VerifyApp --yes --no-commit --no-build --no-aspire. Do NOT add--no-migration- the initial migration is what makes the stack actually run (it builds WebApi even with--no-build). - Run:
dotnet run --project src/backend/VerifyApp.AppHostin the background. The frontend serves at the base port (defaulthttp://localhost:13000); confirm with a probe, do not assume. - Verify: drive the browser (Playwright), capture screenshots at all required breakpoints and both themes. Save screenshots OUTSIDE the repo (scratchpad) - the revert deletes untracked repo files.
- Preview fixes cheaply: small copy/style fixes can be edited directly in the instantiated tree to preview live before teardown - these edits are throwaway, the real fix is applied pre-init afterwards.
- Teardown:
- Stop Aspire.
git reset --hard "$PRE_INIT_SHA"(the project hook blocks a baregit reset --hard- always pass the explicit target).- Delete untracked init artifacts: verify
git ls-files --others --exclude-standardlists ONLY instantiation files, then remove them (the project hook blocksgit clean- use the list +rm). - Delete gitignored leftovers too: the instantiation's
bin/objoutput is invisible to the untracked listing. Remove the renamed project trees wholesale (rm -rf src/backend/<Name>.* src/backend/tests/<Name>.*), thenfind src/backend -type d -empty -delete. - Remove the Docker containers/volumes created since the snapshot (Aspire volumes are named
<name>-db-data,<name>-storage-data).
- Apply findings pre-init: fixes discovered during verification go into the template files (normal delegation rules), then commit. Repeat the loop if the fix needs visual confirmation.
Evidence
Commit the meaningful screenshots under docs/sessions/assets/<date>-<topic>/ and embed them in the PR description with SHA-pinned raw URLs (https://raw.githubusercontent.com/<owner>/<repo>/<full-sha>/docs/sessions/assets/...) so they survive branch deletion after squash-merge.
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.