From ef1becc27374f8ea51815ce24f1680f1dce5c2af Mon Sep 17 00:00:00 2001 From: Florian Hines Date: Thu, 10 Sep 2026 13:50:13 -0500 Subject: [PATCH] feat(skills): add no-comments guidance --- .kilo/skills/no-comments/SKILL.md | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 .kilo/skills/no-comments/SKILL.md diff --git a/.kilo/skills/no-comments/SKILL.md b/.kilo/skills/no-comments/SKILL.md new file mode 100644 index 0000000000..3bbcdd36b0 --- /dev/null +++ b/.kilo/skills/no-comments/SKILL.md @@ -0,0 +1,26 @@ +--- +name: no-comments +description: Keeps code self-explanatory by preventing and removing low-value comments. Use whenever code is written, changed, or reviewed. +--- + +# No comments + +Comments are a last resort. Prefer names, types, structure, and small focused modules that make behavior obvious. + +Delete or reject comments that: + +- Restate code, types, parameters, or control flow. +- Narrate implementation steps or test setup. +- Serve as banners, separators, history, apologies, or commented-out code. +- Explain confusing local code that should instead be clarified by a small code change. + +Keep only comments that preserve information code cannot express: + +- Legal or license headers. +- Non-obvious business rules, edge cases, invariants, or security rationale. +- External platform, vendor, dependency, or protocol constraints. +- Public API contracts for external consumers. +- Current issue, specification, ADR, or RFC links explaining a constraint. +- Required formatter, compiler, coverage, generated-file, or lint directives. + +During review, flag unnecessary comments and misleading or stale comments. Do not shorten narration into different narration. Remove it or make the code explain itself.