Enforces minimal single-line comment policy across TypeScript, Astro, and CSS files.
npx skills add https://github.com/malikkotb/shellpluscore --skill comments-malikkotb
Please help me install this Agent Skill. Skill: comments Source: https://github.com/malikkotb/shellpluscore/tree/main/.agents/skills/comments Command: npx skills add https://github.com/malikkotb/shellpluscore --skill comments-malikkotb
@ts-* and biome-ignore directives, and aria rationale comments. - Use Case: While reviewing a pull request in an Astro project, apply this Skill to strip per-element narration and section banners from .tsx and .astro files while keeping a comment explaining a deliberate workaround. ## Quick Start Review the comments in this file and remove any that fail the smell test while keeping only those that explain a non-obvious why.High-intent search queries and answers about installing and using this skill.
Keep a comment only when it explains a non-obvious why, such as a workaround, a magic value's meaning, or a load-bearing ordering. Delete comments that restate the next line, narrate visible structure, span multiple lines, or mark empty slots as for-later.
Write at most one line per comment, using `{/* ... */}` in Astro markup and standard syntax in TypeScript. The comment must explain intent a reader cannot infer from names, types, or the code itself.
No. Empty slots are self-explanatory, and out-of-scope or for-later notes are prohibited in the markup. If the work genuinely needs tracking, it belongs in an issue tracker rather than a code comment.
Never delete license headers, `@ts-expect-error` and other `@ts-*` directives, `biome-ignore` comments, or aria rationale notes. Also avoid hand-editing generated files like `sanity/types.ts` or `.astro/types.d.ts`.
Never. The policy requires every comment to fit on one line; if a why needs two lines, cut it to the essential clause or delete it. Multi-line banners, preambles, and section dividers are explicitly banned.
LedgerHQReduces unnecessary code comments by replacing them with clearer naming and structure.
marchattonAutomate GitHub pull request merging with rebase or squash strategies.
svoRefactor Python code into self-documenting structure with expressive names.
JSai23Generate and update code documentation from docstrings across Python, Rust, TypeScript, and Go projects.