What problem does it solve? Code comments rot quickly: they contradict the code after refactors, narrate what the code already says, and mislead engineers debugging at 3am. This Skill provides a decision framework for what deserves a comment, how to phrase it so it survives refactors, and how to review comments in pull requests. ## Core Features & Use Cases - Comment triage workflow: A seven-step process covering when to comment (whys, constraints, external anchors), how to phrase comments against behavior rather than positions, and when to delete instead of update. - Docstring guidance: Documents contracts (edge cases, exceptions, side effects) instead of restating signatures, plus TODO hygiene requiring a ticket or owner. - Review checklist and red flags: A three-question review pass, a rationalizations table countering common excuses, and a verification checklist for PRs. - Use Case: While reviewing a PR full of narration comments like "// increment i", apply the review pass to delete redundant comments, rewrite the one durable constraint comment with an external anchor, and flag bare TODOs missing ticket references. ## Quick Start Review the comments and docstrings in my pull request diff and tell me which ones to keep, rewrite, or delete.
