validation
Skill1 starsChanged 9 months agoMITView on GitHub
Validate a package change before committing. Use after editing any Nix expression — covers the evaluation, build, and format checks, reading common eval and build errors, and the full pre-commit checklist.
20 other projects use a version of this.
Adopted by
Most recently taken up by
- thistleknot/skillstheir own version, first seen Nov 8, 2026
- GoogleCloudPlatform/cloud-solutionstheir own version, first seen Nov 8, 2026
- LeanMeanCleanApps/CleanModelContextProtocoltheir own version, first seen Nov 8, 2026
- AnyOrgName/php-skillstheir own version, first seen Nov 8, 2026
- ruujOnChain/HedgeFund-Skillstheir own version, first seen Nov 8, 2026
- honeydew-ai/honeydew-ai-coding-agents-pluginstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use testing.
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.
NVIDIASkilltesting
Run Python and Rust tests for physicsnemo-curator using uv + pytest with coverage reporting via pytest-cov, and cargo-nextest for Rust tests. Includes benchmark workflows with pytest-benchmark and criterion.
Also in 3 projects that use this
Other versions20 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 20
- openai/codex-security★ 11ksame name
- openai/plugins★ 7.8ksame name
- GoogleCloudPlatform/cloud-solutions★ 139same name
- richard-kim-79/archora-skills★ 49same name
- honeydew-ai/honeydew-ai-coding-agents-plugins★ 43same name
- wolverin0/claude-skills★ 41same name
- loocor/mcpmate★ 35same name
- ruujOnChain/HedgeFund-Skills★ 17same name
- aibtcdev/skills★ 11same name
- AnyOrgName/php-skills★ 4same name
10 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 repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- cmakeSkill
- ekala-cmake-nixSkill
- ekapkgs-repoSkill
- goSkill
- mesonSkill
- mk-many-variantsSkill
- nix-buildSkill
- nix-evalSkill
- packagingSkill
- portingSkill
- pythonSkill
- rustSkill
- structured-attrsSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 20 edited versions we read keep these.
4
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 8
All package changes must pass three validation steps:
- Distinctive: line 12
Verify Nix expression evaluates correctly:
- Distinctive: line 27
Verify package builds successfully:
- Distinctive: line 44
Ensure code follows formatting standards:
- Very specific: line 70
DO NOT: search top-level.nix with grep.
“Common” is measured: kept by at least 6 in 10 of the 20 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
Package Validation
All package changes must pass three validation steps:
1. Evaluation Check
Verify Nix expression evaluates correctly:
nix-instantiate -A <package-name>Expected: /nix/store/abc123...-package-1.0.0.drv
For non-derivations:
nix-instantiate --eval -A <attribute>2. Build Check
Verify package builds successfully:
nix-build -A <package-name>Expected: result symlink to /nix/store/xyz789...-package-1.0.0
Inspect results:
ls -la result/
./result/bin/example --version
ldd result/lib/libexample.so3. Format Check
Ensure code follows formatting standards:
nix fmt <path-to-file>Format all modified files:
git diff --name-only '*.nix' | xargs -I {} nix fmt {}Checking Dependencies
Verify dependencies exist before porting:
# Single dependency
nix-instantiate -A zlib
# Multiple dependencies
for dep in acl lzo cmocka zlib zstd; do
echo -n "$dep: "
nix-instantiate -A $dep >/dev/null 2>&1 && echo "✓" || echo "✗"
doneDO NOT search top-level.nix with grep. Packages in pkgs/ and pkgs-many/ are auto-registered.
Common Errors
Evaluation Errors
Missing dependency:
error: attribute 'somelib' missingPort the dependency or add TODO comment.
Syntax error:
error: syntax error, unexpected ')'Fix the syntax in the Nix expression.
Build Errors
Missing build tool:
error: Program 'pkg-config' not foundAdd to nativeBuildInputs.
Missing library:
/nix/store/.../bin/ld: cannot find -lzAdd to buildInputs.
Test failures: Tests are disabled by default. Investigate or keep disabled.
Complete Validation Workflow
# Validate a package
PACKAGE="example"
# 1. Evaluate
nix-instantiate -A $PACKAGE
# 2. Build
nix-build -A $PACKAGE
# 3. Test result
./result/bin/$PACKAGE --version
# 4. Format
nix fmt pkgs/$PACKAGE/default.nixValidation Checklist
nix-instantiate -A <package>succeedsnix-build -A <package>succeeds- Built binary/library works
- All dependencies verified with
nix-instantiate nix fmtrun on all edited files- No
meta.maintainersormeta.teams - TODO comments for missing dependencies
Advanced Validation
Check closure size:
nix-store -q --tree $(nix-build -A example --no-out-link)Check runtime dependencies:
nix-store -q --references $(nix-build -A example --no-out-link)Rebuild from scratch:
nix-build -A example --rebuildReproducibility check:
nix-build -A example --checkDoes 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.

