no-comments
From the author
Use when asked to audit comments in code files and propose structural replacements or deletions with per-candidate approval. Not for deterministic commented-out-code removal: use deslop.
Install
npx skills add OutlineDriven/outline-driven-development --skill no-comments -a claude-code
Installs to .claude/skills/no-comments/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 82
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- deslopmichael-denyer/pstack-claudeRemove AI-generated code slop and clean up code styleEngineering★ 3.4K
- lean-commentsgithub/awesome-copilotAudits, writes, and refines maintained first-party source-code comments and declaration-level documentation across languages. Use when adding, editing, reviewing, cleaning up, or auditing comments, doc comments, docstrings, TODO, FIXME, NOTE, suppressions, or other source commentary, including while modifying code and deciding whether a comment is warranted at all. Defaults to no comment unless it preserves meaningful, non-obvious information that cannot reasonably be recovered from the code or nearby repository context.Writing★ 40.4K
- unslopOutlineDriven/outline-driven-developmentUse when prose is drafted or edited, reviewed for AI tells, or the user asks to remove AI patterns, humanize, or add voice. Offers dedash and detool modes. Not for code debris: use deslop.Writing★ 54
- simplifyOutlineDriven/outline-driven-developmentUse when the user says "simplify this diff" or asks for a compression pass over a change-set. Not for dead-code sweeps: use deslop.Engineering★ 54
- comment-checkerwjgoarxiv/litgravityAudit code comments in a diff or named files: keep intent and reasons, remove stale narration, fix misleading text.Engineering★ 166
- slop-codeAgriciDaniel/anti-slopSlop review and repair for source code, tests, configuration, generated documentation, README files, commit messages and pull request descriptions. Use when someone asks to review generated or agent-written code for quality, asks whether a diff is padded or ceremonial, asks about hallucinated or slopsquatted imports, or asks to clean up comments, docstrings, wrapper functions, defensive try/except blocks, or tests that assert nothing. Runs the load-bearing test: delete the comment, wrapper, handler or assertion-free test and name what broke. Runs the package existence scanner over every import. Reviews commit and pull request text for canned policy assurances and preserved-information boilerplate. Reports defects with severity and confidence separated, never an authorship verdict, and never a claim that a diff was machine written.Engineering★ 64
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in