chore(claude): prevent code comment proliferation

[mbevc1]

Instruct Claude to not use excessive code comments

Checklist

• Docs are autogenerated from CLI help — make sure the help text reflects your changes
• Helm chart (charts/k8s-reporter/) updated, if needed. Note: these changes live in a separate PR
• Terraform provider and related changes (terraform-provider-kosli, terraform-aws-evidence-reporter, terraform-aws-kosli-reporter) updated, if needed

[claude]

Claude finished @mbevc1's task in 1m 6s —— View job

---

Review — chore(claude): prevent code comment proliferation

• Read PR context and prior review rounds
• Diff origin/main...HEAD
• Assess placement, wording, and file conventions
• Post feedback

Verdict

Looks good — approve-equivalent, nothing blocking. Docs-only (CLAUDE.md, +6/-0); no Go files touched, so go build / go vet / go mod tidy checks aren't applicable to this diff.

What changed since the earlier rounds

The block landed in the right place and the earlier substantive concerns are resolved:

• ✅ Moved out of ### Principles (slice-granularity list) into ## Working Style: TDD, directly after the loop — where cleanup guidance belongs.
• ✅ Also make sure to: is now its own lead-in sentence rather than being grammatically glued to "…then commit any remaining cleanup", so the bullets read as standing rules instead of post-commit steps.
• ✅ Bullets use - to match the other 45 bullets in the file.
• ✅ The double-em-dash is gone — not *what*; the code already says… now separates the two independent clauses cleanly.
• ✅ Repeat steps 2–7 is accurate again (the loop is back to 7 steps).
• ✅ Carving out godoc comments on exported identifiers is the right call — a blanket "minimal comments" rule would otherwise fight Go convention and golint-style expectations.

Remaining nits (optional)

Two cosmetics, left inline with a suggestion:

1. Hard wrap — CLAUDE.md:119-121 wraps at ~95 chars; every other bullet/paragraph in the file is a single unwrapped line, making this the only wrapped block in the document.
2. Repeated verb — "Follow good practices — follow industry practices…"; the useful half is "the patterns already established in this codebase".

Neither affects how Claude reads the file. Merge as-is if you'd rather stop iterating.

One thing worth considering

## Working Style: TDD scopes these rules to the TDD loop. Since "keep comments minimal" and "follow existing patterns" apply to all work in this repo (doc edits, config, one-off fixes), a top-level ## Code Style section would be marginally more discoverable. Given the file is read whole on every session, this is a stylistic preference, not a functional gap. Fix this →

---

_{Note: the checked-out working tree had this change reverted locally (M CLAUDE.md) — a runner artifact; I did not commit anything. Review is against the pushed commit b678f83.}
· 20260829_claude_comments