Code style
38 portable Agent Skills for disciplined, reviewable AI-assisted work across Codex, Claude Code, GitHub Copilot, and compatible agents.
npx -y skills add nevitonsantana/adaptive-skills --skill code-styleAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 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.
- 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
Keep code readable, cohesive, and easy to change without turning style into dogma.
SKILL.md
1.8 KB, as published. Nobody here has run it
Overview
Use this skill to improve the reading experience of code: naming, cohesion, file focus, and everyday maintainability.
When to Use
- writing new code
- reviewing existing code
- small focused cleanup
When NOT to Use
- as a substitute for architecture or testing
- to justify broad rewrites with no value proof
Core Moves
- Protect the intended behavior.
- Prefer the smallest clear design.
- Check names and reading flow.
- Keep files and functions focused.
Optional Modules
- Consistency pass — Align with established local conventions when they are sensible.
- Debt note — Name the most important leftover debt without opening unrelated work.
- Extraction hint — Suggest a follow-up refactor if cohesion is still weak after the local fix.
Activation Triggers
- Use consistency pass when the repository already has a strong local convention.
- Add a debt note when you deliberately leave an issue behind.
- Use extraction hint when the file stays overloaded after the current change.
Expected Output
- clearer code
- better names
- more focused structure
Verification
- The code reads in the same order that it executes conceptually.
- Naming reflects intent rather than implementation trivia.
- The file did not become a dumping ground.
Handoff Signals
- The file-level problem is really architectural.
- The change now requires a broader cleanup outside the current scope.
Pairs Well With
refactoringtestingworkflow
Anti-patterns
- Arguing style without user or maintenance impact.
- Adding cleverness that shortens code but hurts readability.
- Hiding design problems behind formatting.