agentleFS
ekala-projectekala-project/ekala-claude-skills/skills/validation/SKILL.md

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

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.
  • NVIDIASkill

    testing

    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

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
  1. Distinctive:

    All package changes must pass three validation steps:

    line 8
  2. Distinctive:

    Verify Nix expression evaluates correctly:

    line 12
  3. Distinctive:

    Verify package builds successfully:

    line 27
  4. Distinctive:

    Ensure code follows formatting standards:

    line 44
  5. Very specific:

    DO NOT: search top-level.nix with grep.

    line 70

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.so

3. 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 "✗"
done

DO 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' missing

Port 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 found

Add to nativeBuildInputs.

Missing library:

/nix/store/.../bin/ld: cannot find -lz

Add 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.nix

Validation Checklist

  • nix-instantiate -A <package> succeeds
  • nix-build -A <package> succeeds
  • Built binary/library works
  • All dependencies verified with nix-instantiate
  • nix fmt run on all edited files
  • No meta.maintainers or meta.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 --rebuild

Reproducibility check:

nix-build -A example --check

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.