BumpyClock/agent-templates / skills_archive/pstack/no-comments
no-comments
UnverifiedReview and remove unnecessary comments while preserving unresolved constraints.
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 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.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |