verifying-changes
Skill2 starsChanged 47 days agoMITView on GitHub
Chooses and runs the right checks for a change in the Teitunnel repository (targeted Rust and UI tests while iterating, generated files, screenshots, accessibility, performance, end-to-end, then the full pnpm verify) and fixes what they report before committing. Use before every commit or pull request, and when asked to test, check or validate a change.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- PostHog/posthog-fosstheir own version, first seen Nov 1, 2026
- raalarcon9705/gated-dev-agentstheir own version, first seen Nov 1, 2026
- vadimvitvickiy/vv-agent-kittheir own version, first seen Oct 20, 2026
- Mr-Quin/danmaku-anywheretheir own version, first seen Oct 8, 2026
- BuilderIO/agent-nativetheir own version, first seen Oct 8, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- BuilderIO/agent-native★ 7.6ksame name
- PostHog/posthog-foss★ 728same name
- Mr-Quin/danmaku-anywhere★ 550same name
- raalarcon9705/gated-dev-agents★ 0same name
- vadimvitvickiy/vv-agent-kit★ 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 repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- adding-cli-commandsSkill
- adding-doctor-checksSkill
- adding-ipc-commandsSkill
- adding-mcp-toolsSkill
- building-uiSkill
- changing-cloudflare-resourcesSkill
- reviewing-pull-requestsSkill
- writing-docsSkill
- writing-user-facing-textSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
3
Distinctive
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 48
Read the first error, not the last.
- Very specific: line 55
Run the failed step again, then pnpm verify again, until it passes.
- Distinctive: line 57
Don't report a change as done while any check fails.
- Distinctive: line 67
Commit messages are Conventional Commits, without AI attribution.
“Common” is measured: kept by at least 6 in 10 of the 5 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
Verifying changes
Files changed in the working tree:
!git status --short
While iterating: run what the change touches
| Changed | Run |
| A Rust crate | CARGO_INCREMENTAL=0 cargo nextest run -p <package> -E 'test(<name>)' |
| Planner output | the planner tests, then cargo insta review: read every snapshot diff |
| A Tauri command or an IPC type | pnpm bindings, then the UI tests that use it |
| UI code | pnpm --filter @teitunnel/desktop test -- <pattern> |
| A screen's look | pnpm --filter @teitunnel/desktop shoot /tmp/shots <route> in light and dark, and look at the images |
| Colours, text or focus order | pnpm --filter @teitunnel/desktop a11y <route> |
| Lists, charts, log views | pnpm --filter @teitunnel/desktop perf (add inspector for the Inspector list) |
| CLI definitions | UPDATE_DOCS=1 cargo test -p teitunnel-cli --bin teitunnel-cli docs |
| Token template, scopes or capabilities | UPDATE_DOCS=1 cargo test -p teitunnel-core --test permissions_doc |
locales/en.json | pnpm --filter @teitunnel/desktop test -- i18n and cargo build -p teitunnel-core |
New UI strings, imports on the startup path, a route's validateSearch | pnpm --filter @teitunnel/desktop build:web && node apps/desktop/scripts/check-bundle-size.ts (the 250 KB initial JS budget; CI's Web job runs it, pnpm verify doesn't). A route file's static imports load with the app: import small helpers from their own module, not a feature's index |
| Website or docs | pnpm --filter @teitunnel/web test and pnpm --filter @teitunnel/web build |
| Flows across app, engine and Cloudflare | pnpm --filter @teitunnel/desktop e2e:build && pnpm --filter @teitunnel/desktop e2e |
| Native look, windows, tray, materials | pnpm build and try the packaged app |
Rust packages: teitunnel-core, teitunnel-cf-api, teitunnel-cloudflared, teitunnel-lens,
teitunnel-mcp, teitunnel-control, teitunnel-localdomains, teitunnel-cli,
teitunnel-desktop, fake-cloudflare, fake-cloudflared.
Before committing: everything
pnpm verifyIt runs Biome, the version check, tsc for the app and website, rustfmt, clippy with
-D warnings, Vitest, the website tests, cargo nextest for the workspace and
cargo deny. It must exit 0.
When something fails
- Read the first error, not the last. Fix the cause, not the symptom.
- Formatting:
pnpm fmt(orcargo fmt --allandpnpm exec biome check --write). - Clippy: fix the code;
#[allow]only with a comment saying why it's right here. - A failing test you didn't touch: find out why before changing it. A test is changed only when the behaviour it pins was meant to change.
- Stale generated files (
bindings.ts,cli.mdx,permissions.mdx): regenerate them with the commands above; never edit them by hand. - Run the failed step again, then
pnpm verifyagain, until it passes.
Don't report a change as done while any check fails; say which check fails and why.
Before opening the pull request
- The change works as a person would use it, not only in tests (run it in
pnpm dev, or the CLI, against a test account or the fakes). - UI changes have light and dark screenshots.
- Docs updated (see
writing-docs). - Any skill in
.claude/skills/that describes what you changed still matches the code; update it in the same pull request (see "Keep this guidance current" inAGENTS.md). - Commit messages are Conventional Commits, without AI attribution.
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.