code-conventions
Skill1 starsChanged 4 months agoMITView on GitHub
Loaded automatically by execute-task and verify-task for any code change - covers comments, abstraction limits, dependency rules, and project-specific conventions from docs/CODE_CONVENTIONS.md. Do not invoke standalone unless the user specifically asks about coding conventions
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
- Distinctive: line 25
No helper extraction unless used in 3+ places.
- Distinctive: line 26
No feature flags or backwards-compat shims - change the code directly.
- Distinctive: line 30
No circular imports between modules.
- Distinctive: line 31
Prefer explicit imports over wildcard/glob imports.
- Very specific: line 35
Read docs/CODE_CONVENTIONS.md for this project's conventions: type system, naming, module structure, error handling, logging, and …
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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
Code Conventions
When to use
Auto-loaded by execute-task and verify-task for any code change. Validate against these conventions before reporting done. If the user asks about conventions directly, invoke this skill standalone.
Universal principles
Comments
Explain non-obvious constraints, invariants, or bug workarounds. For deliberate simplifications, state the known operating limit and an observable trigger for revisiting the design.
Abstraction limits
- Three similar lines is better than a premature abstraction.
- No helper extraction unless used in 3+ places.
- No feature flags or backwards-compat shims - change the code directly.
Dependencies
- No circular imports between modules.
- Prefer explicit imports over wildcard/glob imports.
Project-specific conventions
Read docs/CODE_CONVENTIONS.md for this project's conventions: type system, naming, module structure, error handling,
logging, and stack-specific rules. That file is filled by repo-scan and maintained by the team.
Project-specific rules in docs/CODE_CONVENTIONS.md override the universal principles above when they conflict.
Handoff
- Report: the standard applied to the parent skill's work.
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- 0xkangl/skills★ 1same name
- kennguyen887/agent-foundation★ 1same name
- andresnator/agents-orchestrator★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository21 other files it gives its agents.
- address-feedbackSkill
- brainstormSkill
- comprehensionSkill
- debugSkill
- definition-of-doneSkill
- execute-taskSkill
- migrate-docsSkill
- pr-reviewSkill
- repo-scanSkill
- requirement-analysisSkill
- securitySkill
- setupSkill
- start-ritusSkill
- syncSkill
- task-generationSkill
- tddSkill
- testing-policySkill
- ticket-reviewSkill
- triageSkill
- verify-taskSkill
- wrap-upSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.