Nix coding

Skill YuanshengClaw/yuansheng-kit/.agents/skills/nix-coding

Agent-oriented toolkit for RISC-V optimization knowledge extraction, pattern mining, real-hardware performance analysis, root-cause diagnosis, and code generation

Install

npx -y skills add YuanshengClaw/yuansheng-kit --skill nix-coding

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

3 things to look at

16 days oldThe repository was created 16 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Rewrite, refactor, or review Nix code to follow this repository's custom Nix coding style. Use when asked to restyle, normalize, modernize, reorganize, or otherwise edit .nix files according to the bundled Nix style guide.

SKILL.md

2.1 KB, as published. Nobody here has run it

Nix Coding

Use this skill to change Nix code shape and formatting while preserving behavior.

Required workflow

Identify the target .nix files from the user request, staged diff, or local repository context.
Read references/nix-coding-style.md, relative to this skill directory.
Inspect nearby Nix code before editing so local conventions can override generic guidance where the style reference allows it.
Rewrite only the requested or clearly relevant Nix code. Preserve behavior, public interfaces, option names, package choices, and module wiring unless the user explicitly asks for semantic changes.
Prefer structured Nix edits over text-only reshuffling. Keep generated, vendored, lock, or machine-produced files unchanged unless the user names them.
Format changed .nix files with the repository formatter. If the repository has no formatter command, use nixfmt --width 50 when available.
Run the narrowest practical validation for the touched code, such as formatter checks, Nix evaluation, or existing repository checks.
Report the changed files, validations run, and any validation that could not be run.

Refactor priorities

Apply the bundled style guide before making broader cleanups.
Preserve local order when order affects semantics, precedence, activation behavior, fallback behavior, or user-visible priority.
Keep comments only when they explain non-obvious intent, workarounds, or behavior.
Prefer small, reviewable rewrites over architecture changes.
Do not introduce new helper abstractions solely to satisfy formatting.

Reference

The full style contract is in references/nix-coding-style.md. Load it before changing Nix code, and use it as the source of truth for formatting, expression shape, naming, comments, flakes, packages, and module idioms.