small-fix
Skill73 starsChanged 58 days agoApache-2.0View on GitHub
Make a small, reviewable NeMo Fabric bug fix without widening scope unnecessarily. Use for narrowly scoped bug fixes or behavior corrections in NeMo Fabric.
In this repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- check-release-deploymentsSkill
- contribute-adapterSkill
- contribute-apiSkill
- contribute-docsSkill
- create-beta-tagSkill
- create-rc-tagSkill
- create-release-tagSkill
- draft-release-notesSkill
- karpathy-guidelinesSkill
- maintain-ciSkill
- maintain-packagingSkill
- prepare-code-freezeSkill
- prepare-prSkill
- python-testsSkill
- qualify-harborSkill
- review-doc-styleSkill
- update-project-versionSkill
- validate-changeSkill
- code-reviewSkill
- swebench-debuggingSkill
- nemo-fabric-build-adapterSkill
- nemo-fabric-integrateSkill
- alternateSkill
- defaultSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
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
- Very specific: line 13
Use karpathy-guidelines alongside this skill for implementation or review work.
- Distinctive: line 17
Use this skill for narrowly scoped bug fixes or behavior corrections.
- Distinctive: line 22
Keep the change as small as possible
- Distinctive: line 23
Avoid opportunistic refactors unless they are required to fix the bug safely
- Distinctive: line 24
Add or update the smallest meaningful test that proves the fix
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Contribute A Small Fix
Companion Guidance
Use karpathy-guidelines alongside this skill for implementation or review
work. Keep changes scoped, surface assumptions, and define focused validation
before editing.
Use this skill for narrowly scoped bug fixes or behavior corrections.
Rules
- Reproduce or identify the failing behavior first
- Keep the change as small as possible
- Avoid opportunistic refactors unless they are required to fix the bug safely
- Add or update the smallest meaningful test that proves the fix
Checklist
- Scope of the fix is explicit
- Affected language surfaces are understood
- A regression test or focused validation path exists
- Docs updated if public behavior changed
- PR notes can explain what failed before and why the fix is safe
References
README.mdjustfilekarpathy-guidelines
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.