claude-dev-env 8.46.4 → 8.46.5

package/.agents/agents-archived/clean-coder.md

@@ -135,7 +135,7 @@ Consult the advisor the spawn ticket names. When the ticket names the orchestrat
 [3] Parameters and returns typed; no Any / no type-ignore directives?
 [4] Do not add code comments. Preserve existing comments. Docstrings remain allowed.
 [5] When a change touches code that an existing comment describes or is attached to, remove that comment in the same change and carry its meaning through clear names and structure. Leave comments tied to untouched code unchanged. Keep comment cleanup inside the requested task.
-[6] Production and tests follow one rule. Changed directive, TODO, FIXME, HACK, XXX, and type-ignore comments are removed rather than added or justified.
+[6] Production and tests follow one rule. Changed directive, TODO, FIXME, HACK, XXX, and type-ignore comments are removed. Do not add or justify them.
 [7] Magic values and UPPER_SNAKE live in config/ where required?
 [8] Function short; one job; guards over else-chains?
 [9] Pre-check --check clean for the real destination path?

package/.agents/agents-archived/code-quality-agent.md

@@ -63,7 +63,7 @@ Tradeoff for category-restricted mode: parallel category invocation loses cross-
 
 Leave comments tied to untouched code unchanged. Findings on production and test code report only on new code added by the diff; comments on lines that remain otherwise unchanged stay outside the audit's scope. New inline comments added by this PR's diff are themselves a category J finding (code self-documents through naming).
 When a change touches code that an existing comment describes or is attached to, remove that comment in the same change and carry its meaning through clear names and structure. Leave comments tied to untouched code unchanged. Keep comment cleanup inside the requested task.
-Production and tests follow one rule. Changed directive, TODO, FIXME, HACK, XXX, and type-ignore comments are removed rather than added or justified.
+Production and tests follow one rule. Changed directive, TODO, FIXME, HACK, XXX, and type-ignore comments are removed. Do not add or justify them.
 
 ## Read-Only Stance
 

package/.agents/skills/grok-spawn/reference/worker-briefs.md

@@ -63,7 +63,7 @@ You edit code and run tests for one closed task. You never commit, push, or call
 
 Do not add code comments. Preserve existing comments. Docstrings remain allowed.
 When a change touches code that an existing comment describes or is attached to, remove that comment in the same change and carry its meaning through clear names and structure. Leave comments tied to untouched code unchanged. Keep comment cleanup inside the requested task.
-Production and tests follow one rule. Changed directive, TODO, FIXME, HACK, XXX, and type-ignore comments are removed rather than added or justified.
+Production and tests follow one rule. Changed directive, TODO, FIXME, HACK, XXX, and type-ignore comments are removed. Do not add or justify them.
 
 ## Scope
 

package/AGENTS.md

@@ -68,7 +68,7 @@ Match requested status, paths, links, and format. Name files, checks, blockers,
 
 Do not add code comments. Preserve existing comments. Docstrings remain allowed.
 When a change touches code that an existing comment describes or is attached to, remove that comment in the same change and carry its meaning through clear names and structure. Leave comments tied to untouched code unchanged. Keep comment cleanup inside the requested task.
-Production and tests follow one rule. Changed directive, TODO, FIXME, HACK, XXX, and type-ignore comments are removed rather than added or justified.
+Production and tests follow one rule. Changed directive, TODO, FIXME, HACK, XXX, and type-ignore comments are removed. Do not add or justify them.
 
 Banned word: real
 

package/docs/CODE_RULES.md

@@ -7,7 +7,7 @@ Use this index for edits. [`.cursor/BUGBOT.md`](../../../.cursor/BUGBOT.md) poin
 Do not add code comments. Preserve existing comments. Docstrings remain allowed.
 
 When a change touches code that an existing comment describes or is attached to, remove that comment in the same change and carry its meaning through clear names and structure. Leave comments tied to untouched code unchanged. Keep comment cleanup inside the requested task.
-Production and tests follow one rule. Changed directive, TODO, FIXME, HACK, XXX, and type-ignore comments are removed rather than added or justified.
+Production and tests follow one rule. Changed directive, TODO, FIXME, HACK, XXX, and type-ignore comments are removed. Do not add or justify them.
 
 A keep marker is the one comment that may be added and kept: a comment that opens with a prefix the repository lists under `comment_keep_markers` in `.claude/policy-lint.json`. Open [details](code-rules/comment-preservation.md) when editing comments.
 

package/hooks/blocking/code_rules_comments.py

@@ -201,10 +201,10 @@ def _is_keep_occurrence(comment_text: str, all_keep_markers: tuple[str, ...]) ->
     """Return True for a comment that opens with an accepted keep marker.
 
     A keep marker is meant to be freely added and to survive edits to the
-    line it sits on, unlike ``noqa`` or ``TODO``, which AGENTS.md requires to
-    be removed rather than added or justified. It is excluded here rather
-    than through the shared exempt-marker set that ``check_comment_changes``
-    deliberately still blocks on add.
+    line it sits on. AGENTS.md requires ``noqa`` and ``TODO`` comments to be
+    removed and forbids adding or justifying them. This check excludes keep
+    markers itself, outside the shared exempt-marker set that
+    ``check_comment_changes`` deliberately still blocks on add.
     """
     return comment_text.startswith("#") and comment_text[1:].lstrip().startswith(
         all_keep_markers

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "claude-dev-env",
-    "version": "8.46.4",
+    "version": "8.46.5",
     "description": "Claude Code development standards — rules, hooks, agents, commands, and skills",
     "type": "module",
     "bin": {

package/system-prompts/software-engineer.xml

@@ -116,7 +116,7 @@
   - Preserve existing comments.
   - Do not add code comments.
   - When a change touches code that an existing comment describes or is attached to, remove that comment in the same change and carry its meaning through clear names and structure. Leave comments tied to untouched code unchanged. Keep comment cleanup inside the requested task.
-  - Production and tests follow one rule. Changed directive, TODO, FIXME, HACK, XXX, and type-ignore comments are removed rather than added or justified.
+  - Production and tests follow one rule. Changed directive, TODO, FIXME, HACK, XXX, and type-ignore comments are removed. Do not add or justify them.
   - Express new explanations through self-documenting names
   - Docstrings remain allowed.