Skip to content
Back to skills

No Comments

ASecurity

Review and remove unnecessary comments while preserving unresolved constraints.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 7, 2026
code-quality

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned November 7, 2026

npx -y skills add BumpyClock/agent-templates --skill no-comments --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of No Comments?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for No Comments
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/bumpyclock-no-comments-agent-templates/badge)](https://www.skillsdirectory.com/skills/bumpyclock-no-comments-agent-templates)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: no-comments
description: Review and remove unnecessary comments while preserving unresolved constraints.
disable-model-invocation: true
---

# No comments

Use the caller's files or diff. Otherwise review the current branch diff, including the worktree.
Keep unrelated code and user edits outside the scope.

Use Comment Sicko for a bounded read-only review when that role is available and an independent perspective helps.
Otherwise inspect directly.
Treat the review as evidence to assess, not permission to accept every deletion.

Use the [shared comment policy](../../../defaults/AGENTS.md#code-clarity-and-comments) to assess each candidate deletion.
Keep an ambiguous comment until evidence resolves its purpose.
Do not treat uncertainty as a reason to delete.

When a constraint can use a type, runtime check, test, or lint, propose the smallest in-scope enforcement.
If the user approves that implementation, validate the enforcement before removing the redundant comment.
If approval is absent or the root cause is outside scope, retain the comment and report the unresolved constraint.

Do not turn a comment cleanup into an architecture exercise or unrelated code repair.
Use additional investigation only to resolve a consequential uncertainty.
Validate affected contracts when a change can affect behavior or tool directives.
Report accepted deletions, retained constraints, and validation limits.

Files in this skill

  • SKILL.md1.4 KB
  • agents/openai.yaml273 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.