verify
Skill14 starsChanged 4 months agoMITView on GitHub
Verify a santree-app change end-to-end — run the full green checklist (cargo check/clippy/test, bindings drift, tsc, biome, vitest), then drive the real app via the screenshot harness to observe the change working. Use before committing any nontrivial change, or when asked to confirm something works in the real app.
190 other projects use a version of this.
Adopted by
Most recently taken up by
- Automattic/wp-calypsotheir own version, first seen Nov 16, 2026
- abe238/hotinaitheir own version, first seen Nov 16, 2026
- SmartStudio/baize-bottheir own version, first seen Nov 15, 2026
- YuBan834/vrma-labtheir own version, first seen Nov 15, 2026
- Ju571nK/lodelinetheir own version, first seen Nov 15, 2026
- ericbust/namedroptheir own version, first seen Nov 15, 2026
Used with
Projects with it also use genie-hacks, workfly and 10 more.
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.
automagik-devSkillgenie-hacks
Browse, search, and contribute community hacks — real-world patterns for provider switching, teams, skills, hooks, cost optimization, and more.
Also in 3 projects that use this
automagik-devSkillworkfly
Discover a procedure and build its saved workflow — dynamic discovery, drafted script, adversarial verification, landed in the catalog.
Also in 3 projects that use this
TheKREATORSSkillinstinct-export
Export instincts from project/global scope to a file
Also in 3 projects that use this
TheKREATORSSkillinstinct-import
Import instincts from file or URL into project/global scope
Also in 3 projects that use this
AviadPSkillrisk-assess
Assess the risk and blast radius of a proposed code change before implementing it. Evaluates CI impact, framework-wide vs localized scope, rollback path, and identifies blindspots. Use when user says "what's the risk", "is this safe", "assess the impact", "risk assess", "blast radius", or before applying framework-wide or CI-affecting changes. Do NOT use for code quality review (use code-quality) or plan validation (use design-validator).
Also in 3 projects that use this
diego-tobalinaSkillbuild-fix
Fix build and compilation errors systematically. Run when build fails.
Also in 6 projects that use this
- +2 more from automagik-dev
- +1 more from TheKREATORS
Other versions190 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 190
- react/react★ 253ksame name
- facebook/react★ 253ksame name
- garrytan/gstack★ 142ksame name
- oven-sh/bun★ 97ksame name
- anthropics/financial-services-plugins★ 41ksame name
- anthropics/financial-services★ 41ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- anthropics/claude-quickstarts★ 19ksame name
- NVIDIA-NeMo/Speech★ 19ksame name
180 more not listed
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 repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- new-commandSkill
- production-reviewSkill
- verifySkill
- new-commandSkill
- production-reviewSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 169 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Run in this order (cheapest first).
- Very specific: line 20
If anything touched src-tauri/src/commands.rs, src-tauri/src/lib.rs, or a specta::Type in crates/core/src/domain.rs: pnpm gen:bindings && …
- Very specific: line 33
If an engine crate changed (santree-pty, -host, -remote-proto, -remote-tls, -agent-kind): cargo +1.95 check -p <crate> --all-targets.
- Distinctive: line 50
Do not use them, and do not conclude "no UI change" from one.
“Common” is measured: kept by at least 6 in 10 of the 169 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 a santree-app change
Two passes: static gates first (fast → slow, stop on first failure), then drive the real app and observe the change. A change is verified only when both pass.
Pass 1 — static gates
Run in this order (cheapest first). All must be green:
cargo fmt --all --check— first, and never skipped. Clippy and the tests pass on unformatted code, so nothing else catches this; CI'sbackend-lintjob runs it before clippy, so drift fails the build and hides clippy's verdict. If it reports a diff,cargo fmt --alland re-check.cargo check --workspace- If anything touched
src-tauri/src/commands.rs,src-tauri/src/lib.rs, or aspecta::Typeincrates/core/src/domain.rs:pnpm gen:bindings && git diff --exit-code src/bindings.ts— if the diff is non-empty, the regeneratedbindings.tsmust be part of the change (CI fails on drift). Never hand-edit it. npx tsc --noEmit— and if test files changed, alsopnpm typecheck:test(vitest strips types without checking them; this is the only place test files are type-checked).pnpm lint(Biome: lint + format + import sorting). The frontend half of the same trap —biome checkfails on formatting too, so runpnpm formatand re-check rather than reading past it.cargo clippy --workspace --all-targets -- -D warningspnpm test(vitest) andcargo test --workspace- If an engine crate changed (
santree-pty,-host,-remote-proto,-remote-tls,-agent-kind):cargo +1.95 check -p <crate> --all-targets. CI'sengine-linuxjob also clippies and tests them on Linux, the only platform besides macOS they must build on. - For any new/changed command taking a path, id, or branch: confirm it's
validated (
safe_path/safe_real_path, no leading-) before it reaches fs or git — see AGENTS.md "Security & validation invariants".
Pass 2 — drive the real app
pnpm dev in the background, wait for the window, then observe the affected
flow. Synthetic mouse clicks do NOT work — see harness notes below.
Screenshot harness (WKWebView)
- Synthetic clicks are silently dropped.
osascriptSystem Events clicks reach the OS but never the WebView — they appear to succeed and do nothing. Do not use them, and do not conclude "no UI change" from one. - Keystrokes DO work:
osascript -e 'tell application "System Events" to keystroke "1" using command down'— ⌘1 opens Tickets, ⌘K the palette (type a destination or a PR), ⌘B toggles the sidebar; arrows/tab/enter move focus and activate. Trees, Reviews and Triage tickets are reached from the sidebar. - Capture:
screencapture -x -l <windowId> out.png, then Read the PNG. Get the window id fromscreencapture -l-style listing orosascript -e 'tell application "santree" to id of window 1'. - On non-Retina displays the capture is 1x (pixels == points); take a full-window shot first and compute crop regions from the known layout.
GOTCHA — verify WHICH binary you're looking at
This machine can run TWO processes named santree at once: the dev build
(target/debug/santree, no bundle id) and an installed /Applications/santree.app
(bundle id com.santree.desktop). Targeting by process name can silently hit
the stale installed app and make a real fix look absent (this has caused a
near-misdiagnosis before). Before trusting any observation:
- dev build:
pgrep -f target/debug/santree - installed:
stat -f "%Sm %N" /Applications/santree.app/Contents/MacOS/santree - target by pid —
first application process whose unix id is <pid>— never by bare process name.
Reporting
State plainly what was run and what was observed (screenshot evidence for UI changes). If a gate failed, report the failure output — don't soften it.
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.

