Quality Comments · spxros bundle Write code comments that explain why, not what, and clean up comments that don't. Use whenever writing, reviewing, refactoring, or documenting code, and proactively before emitting any non-trivial code block (more than a few lines, or any public function, class, or exported type) even when comments were never mentioned - over-commenting is the default failure and this prevents it. Also use whenever comments, docstrings, JSDoc, Javadoc, XML doc comments, rustdoc, godoc, header comments, or TODO/FIXME/HACK/XXX/NOTE tags come up, and for requests like "document this function", "add comments", "too many comments here", or "clean up the comments". Covers doc-comment contracts for public APIs, inline why-comments for maintainers, per-language conventions (Python, JS/TS, Go, Rust, Java, C#, C/C++, Swift, Ruby, PHP, shell), task-tag quality standards, and a flag-and-ask workflow for removing redundant comments without ever deleting them unasked.
