gs-no-comments
No comments
Get a report of the bad comments in the scope, delete them, then act on the findings you accept.
The report comes from gs-find-bad-comments, which holds the rules: what it keeps, when it gives code a reshape verdict, how it treats suppressions, and what it reports. This skill needs that skill and has no rules of its own for finding comments. Defer to the report's fresh perspective. Do not restate or soften its rules.
Scope
Use the files or diff the user names. Otherwise use the current diff against the default branch, including the working tree. Find the default branch with git symbolic-ref --short refs/remotes/origin/HEAD, then git remote show origin, then main.
Steps
-
Get the report and make its deletions. Take the first of these that applies.
- The user hands you a report that
gs-find-bad-commentsalready made. Check that each comment it names is still where the report says. gs-find-bad-commentsis installed. Start one subagent with the harness's subagent tools, and have it run that skill on the scope.gs-find-bad-commentsis not installed. Stop before you change any file. Ask the user to install it withnpx skills add agoodway/goodstack --skill gs-find-bad-comments, and to run this skill again. Do not judge the comments from memory of its rules.
Use the model the user names, otherwise the strongest the harness reaches, otherwise the session's model. If the harness has no subagent tools, run the pass yourself and say so. Re-read every file in scope from disk first, and judge each comment against the rules alone, not against what you remember from this session. Write the report before you start step 2.
- The user hands you a report that