@staff0rd/assist 0.300.0 → 0.301.0

package/README.md

@@ -58,6 +58,7 @@ After installation, the `assist` command will be available globally. You can als
 - `/journal` - Append a journal entry summarising recent work, decisions, and notable observations
 - `/next [id]` - Signal completion and chain into the next backlog item; pass an `id` to run a specific item directly (falls back to the picker if the id is missing, done, won't-do, or blocked)
 - `/standup` - Summarise recent journal entries as a standup update
+- `/strip-comments` - Enforce self-documenting code: declare the comment policy in CLAUDE.md if absent, then strip redundant comments, commented-out code, and section banners from tracked source files (functional directives and genuine workaround comments are preserved); edits are left unstaged
 - `/sync` - Sync commands and settings to ~/.claude
 - `/test-cover` - Incrementally increase test coverage by identifying and testing uncovered files
 - `/test-review` - Review existing tests for quality, coverage gaps, and adherence to conventions

package/claude/commands/strip-comments.md

@@ -0,0 +1,53 @@
+---
+description: Enforce self-documenting code by declaring the comment policy and stripping redundant comments
+---
+
+You are enforcing a self-documenting code style: code should explain itself, and comments should only earn their place when they convey something the code cannot.
+
+## Step 1: Ensure CLAUDE.md declares the policy
+
+Read `CLAUDE.md` at the repository root.
+
+Decide whether it already states a code-style or commenting policy — look for an existing `## Code style` heading, a `## Commenting code` (or similar) section, or any prose that tells contributors not to write comments that restate the code.
+
+- If such a policy is **already present**, leave `CLAUDE.md` unchanged. Do not duplicate or reword it.
+- If **no** such policy exists, append the following section verbatim (including the heading) to the end of `CLAUDE.md`:
+
+```markdown
+## Code style
+
+Write self-documenting code. Do not add comments that restate what the code already says, label obvious sections, or narrate standard logic and syntax. Only comment when a line involves unintuitive complexity, a genuine hack, or a workaround that the code itself cannot make clear. Never leave commented-out code in the tree.
+```
+
+## Step 2: Enumerate tracked source files
+
+List git-tracked source files with `git ls-files`. Restrict to source files (e.g. `.ts`, `.tsx`, `.js`, `.jsx`, `.cs`, `.py`, `.go`, `.rs`, `.java`, `.kt`, `.rb`, `.c`, `.h`, `.cpp`, `.css`, `.scss`, `.sh`). Skip generated output, lockfiles, vendored dependencies, and markdown/docs.
+
+## Step 3: Remove violating comments
+
+Read each file and remove only comments that violate the policy:
+
+- **Redundant explanatory comments** that restate what the adjacent code plainly does (e.g. `// increment counter` above `counter++`).
+- **Commented-out code** — dead code left in the tree.
+- **Section-banner comments** that merely label a region (e.g. `// ---- helpers ----`, `// === Setup ===`).
+
+**Never remove** the following, even if they look like noise:
+
+- **Functional directives** that the toolchain acts on: `eslint-disable*`, `@ts-expect-error`, `@ts-ignore`, `biome-ignore`, `prettier-ignore`, `// @ts-nocheck`, coverage pragmas (`c8 ignore`, `istanbul ignore`), `noqa`, `type: ignore`, `#pragma`, `//go:`-style directives, and similar.
+- **Comments marking a genuine hack or workaround** — anything explaining *why* non-obvious code exists, including `HACK`/`WORKAROUND`/`FIXME`/`TODO` notes, links to issues, or rationale the code cannot convey on its own.
+- **Doc comments** that form part of an API contract (JSDoc/TSDoc, XML doc comments, docstrings) unless they only restate the signature.
+
+When in doubt, keep the comment. The cost of leaving a borderline comment is far lower than deleting one that carries intent.
+
+## Step 4: Apply as unstaged edits and summarise
+
+Apply every removal directly to the working tree using Edit. **Do not stage and do not commit** — leave all changes unstaged for the user to review.
+
+Then print a per-file summary, for example:
+
+```
+src/foo.ts        3 removed
+src/bar/baz.ts    1 removed
+```
+
+For each file with removals, list the removed comments (a short quote of each) so the user can audit the changes. End with the total count and a reminder that the edits are unstaged and ready for review.

package/claude/settings.json

@@ -80,6 +80,9 @@
 			"SlashCommand(/handover)",
 			"Skill(recall)",
 			"SlashCommand(/recall)",
+			"Skill(strip-comments)",
+			"SlashCommand(/strip-comments)",
+			"Bash(git ls-files:*)",
 			"WebFetch(domain:staffordwilliams.com)"
 		],
 		"deny": [

package/dist/index.js

@@ -6,7 +6,7 @@ import { Command } from "commander";
 // package.json
 var package_default = {
   name: "@staff0rd/assist",
-  version: "0.300.0",
+  version: "0.301.0",
   type: "module",
   main: "dist/index.js",
   bin: {

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@staff0rd/assist",
-	"version": "0.300.0",
+	"version": "0.301.0",
 	"type": "module",
 	"main": "dist/index.js",
 	"bin": {