no-comments

Files (1)

• SKILL.md

SKILL.md (first lines)

# No comments

The existing **comments** skill owns comment classification, scope, and surgical deletion. Do not duplicate its rubric here.

## Steps

1. Apply the **comments** skill to the caller's files or diff. Otherwise use its default working-tree scope.
2. Review its edits. Reject application-code changes, scope escapes, and deletions protected by the comments skill's pragma, license, or meaningful-follow-up exceptions.
3. Before keeping or deleting an ambiguous `IMPORTANT`, `do not remove`, or similar claim, run **how** or **why** on the affected symbol. If the claimed constraint is false or unproven, delete the comment.
4. Fix trivial accepted findings directly by deleting dead code, dropping an unused parameter, or using the real API. If a fix changes structure across a function boundary, run **architect** first.
5. Replace enforceable directives with the cheapest real mechanism in scope: a type, runtime invariant, behavior test, or CI lint. Delete the superseded comment. If enforcement is out of scope or not approved, leave the valid comment and report the open mechanism instead of pretending the constraint disappeared.
6. Verify the touched code with the narrowest relevant analyzer or behavior check. Report what changed, any comment restored after review, encodings added, and open constraints.

Use the **pstack-runtime** contract for any independent comment reviewer. The parent applies and verifies changes; a reviewer never edits application code.

From IgorKhramtsov/pstack-skills, MIT.

More from IgorKhramtsov/pstack-skills