Node
One-command harness distribution for coding agents — a versioned YAML catalog projected into agent instructions, skills, and deterministic git gates.
npx -y skills add niksavis/basicly --skill nodeAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 24 days oldThe repository was created 24 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.
- 1 stars1 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
Use Node and npm in this repo for the markdownlint git hook and other node tooling. Use when running npm or npx committing or pushing from a script or background job on WSL or debugging a node-based hook that resolves the wrong node binary.
SKILL.md
1.8 KB, as published. Nobody here has run it
Node
Node in this repo is narrow but load-bearing: the markdownlint git hook runs
npx --no-install markdownlint-cli2, resolving the markdownlint-cli2
devDependency pinned in package.json / package-lock.json. If the wrong node
is on PATH, that hook breaks and blocks commits.
The WSL non-interactive-shell trap (the one that bites)
A login shell sources your profile, which loads the version manager (nvm) and
puts the repo's node on PATH. A non-interactive shell — a script, a
background job, a git hook launched by a headless agent — does not source
that profile, so npx/node can resolve to a Windows node install reached over
WSL interop instead of the Linux one. markdownlint (and any node-based hook) then
runs under the wrong node, or fails outright, only from scripts and background
jobs — never when you commit by hand in your terminal.
Fix: put the repo's node on PATH before you commit or push from a script or
background job. The exact recipe is in
references/wsl-node-path.md.
npm hygiene
npm ci(notnpm install) for a reproducible install frompackage-lock.json; commit the lockfile with any dependency change.npx --no-install <tool>runs the pinned local devDependency and refuses to silently fetch a different version from the network — keep the--no-install.- Keep the node footprint minimal: this repo ships one devDependency on purpose. Adding a dependency is a confirmation-gated change, not a reflex.