lean-verification
Skill501 starsChanged 16 days agoApache-2.0View on GitHub
Run build/lint/test/typecheck verification during implementation or before merge while minimizing token spend. Use instead of raw Nx or Vitest commands, especially during an OpenSpec task slice.
- Deletes or force-pushes
2 other projects use a version of this.
Adopted by
Most recently taken up by
- matt-w-horn/lean-skillstheir own version, first seen Nov 1, 2026
- LeonardSEO/ambitious-math-researchtheir own version, first seen Oct 13, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- matt-w-horn/lean-skills★ 1same name
- LeonardSEO/ambitious-math-research★ 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 repository59 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/a11y.mdcCursor rule
- nx-generateSkill
- nx-importSkill
- nx-pluginsSkill
- nx-run-tasksSkill
- nx-workspaceSkill
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-exploreSkill
- openspec-proposeSkill
- openspec-sync-specsSkill
- address-current-branch-reviewSkill
- api-designSkill
- celebration-scene-ideasSkill
- code-review-and-qualitySkill
- create-ticketSkill
- dep-scanSkill
- dep-triageSkill
- dial-docsSkill
- extract-to-libSkill
- figmaSkill
- fix-cve-backportSkill
- git-shipSkill
- i18n-stringsSkill
- lib-themingSkill
- monitor-ciSkill
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-exploreSkill
- openspec-proposeSkill
- openspec-sync-specsSkill
- proactive-security-monitorSkill
- refactoring-auditSkill
- chat-release-notesSkill
- responsive-designSkill
- security-monitor-triagerSkill
- snyk-jira-ingestSkill
- snyk-scan-stubSkill
- snyk-triageSkill
- ui-kit-reviewSkill
- nx-generateSkill
- nx-pluginsSkill
- nx-run-tasksSkill
- nx-workspaceSkill
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-exploreSkill
- openspec-proposeSkill
- nx-generateSkill
- nx-importSkill
- nx-pluginsSkill
- nx-run-tasksSkill
- nx-workspaceSkill
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-exploreSkill
- openspec-proposeSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
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
- Very specific: line 8
Use the narrowest verification tier that can disprove the current change.
- Very specific: line 57
Before removing the worktree, remove the link first (cmd /c rmdir <worktree>\node_modules on Windows, rm <worktree>/node_modules …
- Distinctive: line 70
Use the printed failure excerpt first.
≈ “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
Lean verification
Use the narrowest verification tier that can disprove the current change. The
scripts capture full output under tmp/agent-logs/; successful runs return a
two-line status, while failures return a bounded excerpt and the log path.
Verification tiers
# Red/green loop: pass one or more workspace-relative test paths.
npm run test:file -- libs/example/src/Foo.spec.ts
# Completed task or vertical slice: affected projects only.
npm run verify:changed
# Final pre-merge gate: full, non-mutating verification.
npm run verify:fulltest:fileis the default during implementation. It groups paths by their nearest Vite/Vitest config and runs only those files.test:changedandverify:changeduse Nx's affected project graph withorigin/developmentas the base.verify:affectedremains available as an explicit affected verification alias.verify:fulluseslint:check, never the mutatingnpm run lintcommand.build:quietbuilds affected projects when the change can affect bundling.
This workspace contains many Nx projects, so affected verification narrows typecheck, lint, test, and build work to the changed projects and their affected dependents. Prefer exact tests for the mid-task loop; reserve project-level affected checks for a completed slice. A successful affected run may execute no task when only docs or agent configuration changed, so it is not a substitute for the final full gate.
Verifying in a git worktree
A worktree that shares the main checkout's node_modules through a junction
or symlink verifies the wrong tree unless you point Nx at it:
- Set
NX_WORKSPACE_ROOT_PATHto the worktree (andNX_DAEMON=false) for every Nx command. An inherited value runs lint, tests and typecheck against the main checkout, which can be on another branch, and still reports success. Confirm that the VitestRUNline shows the worktree path. - Through the shared
node_modules,@nx/dependency-checks,import/order, "The workspace is out of sync" and baretsc(which resolves@epam/*into the main checkout) report errors that are not in the change. Do not runnx syncand do not "fix" them: lint the changed files withnode node_modules/eslint/bin/eslint.js <files>, run the affected specs, and leave the full typecheck to CI. - Before removing the worktree, remove the link first (
cmd /c rmdir <worktree>\node_moduleson Windows,rm <worktree>/node_moduleselsewhere), thengit worktree remove.git worktree remove --forceandrm -rffollow the link and empty the main checkout'snode_modules.
Verification cadence
Batch related edits for one task-list item before re-verifying. Do not rerun a suite after each individual edit. OpenSpec tasks should name their exact test files so the red/green loop does not require rediscovery.
Failure handling
Use the printed failure excerpt first. Search or read only the relevant portion
of the saved log if that excerpt is insufficient; do not load the whole log or
rerun with a verbose reporter by default. Keep --reporter=minimal so passing
test logs do not enter the conversation.
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.

