build-check
Skill1 starsChanged 37 days agoMITView on GitHub
Full build and type-check of the snipkiwi project with detailed error reporting
5 other projects use a version of this.
Adopted by
Most recently taken up by
- arcasilesgroup/ai-engineeringtheir own version, first seen Nov 8, 2026
- EmeaAppGbb/spec2cloudtheir own version, first seen Oct 9, 2026
- crgarcia12/Liliputtheir own version, first seen Jul 14, 2026
- TheophilusChinomona/idevtheir own version, first seen Jun 12, 2026
- IjonTychy/brain-iostheir own version, first seen Mar 28, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- EmeaAppGbb/spec2cloud★ 100same name
- arcasilesgroup/ai-engineering★ 65same name
- crgarcia12/Liliput★ 4same name
- IjonTychy/brain-ios★ 1same name
- TheophilusChinomona/idev★ 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 repository6 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- test-compareSkill
- test-extractSkill
- test-mcpSkill
- clone-pageSkill
- extractSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
5
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 10
Run a comprehensive build and type-check of the snipkiwi project.
- Distinctive: line 19
Verify dist/ output is generated
- Distinctive: line 20
Check that all expected files exist in dist/:
- Distinctive: line 31
Verify the entry point loads without import errors
- Distinctive: line 37
Import health check result
“Common” is measured: kept by at least 6 in 10 of the 4 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
Build Check
Run a comprehensive build and type-check of the snipkiwi project.
Steps
- Type check (no emit):
npx tsc --noEmit- Report any type errors with file, line, and error message
- Group errors by file
- Full build:
npx tsc- Verify dist/ output is generated
- Check that all expected files exist in dist/:
index.js(CLI entry)mcp-server.js(MCP entry)browser/browser-manager.jsbrowser/viewport-manager.jsextraction/extraction-pipeline.js+ 12 other extraction modulestailwind/css-to-tailwind.js+ 4 other tailwind modulestypes/index.jsutils/parsel.js,utils/helpers.js
- Quick smoke test:
node -e "import('./dist/index.js').catch(e => console.error(e.message))"- Verify the entry point loads without import errors
- Report summary:
- Total TypeScript errors (should be 0)
- Total dist files generated
- Any missing expected files
- Import health check result
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.

