chore(code-comments): clean comment-discipline violations #14

New issue

Closed

opened 2026-06-08 21:50:56 +00:00 by coilysiren · 0 comments

coilysiren commented

2026-06-08 21:50:56 +00:00

Owner

What

The code-comments pre-commit check (ships from agentic-os) targets two patterns Kai wants gone across her repos:

oversized contiguous comment blocks explaining code that is simple on its own
comments documenting the previous state of the world where the prior state does not matter

This repo carries 63 latent violations under the current check (v0.16.0): 0 in code, 63 in YAML.

Why these are latent

This repo pins agentic-os v0.14.0, which does enforce YAML, but no commit has run since the rule landed on 2026-06-04. The existing tree is uncaught and the next commit will fail code-comments until these are cleaned.

Scope

Already on a YAML-enforcing rev. Bump to v0.16.0 while here.
Clean the violations now, before the next commit fails on them.

Top offenders:

parsers/_registry.yml - 6
parsers/dig.yml - 6
parsers/nc-zv.yml - 5
parsers/ping.yml - 5
parsers/ssh-exec.yml - 5
parsers/tailscale-ping.yml - 5

Done when

the repo pins agentic-os v0.16.0 with - id: code-comments active in the managed block
pre-commit run code-comments --all-files passes with no excludes grandfathering, beyond genuinely generated or vendored paths

Cross-repo context: the catalogue was built 2026-06-08. Sibling meta-work is tracked in agentic-os (check changes) and infrastructure (ansible version-sync role).

## What The `code-comments` pre-commit check (ships from agentic-os) targets two patterns Kai wants gone across her repos: * oversized contiguous comment blocks explaining code that is simple on its own * comments documenting the previous state of the world where the prior state does not matter This repo carries **63** latent violations under the current check (v0.16.0): 0 in code, 63 in YAML. ## Why these are latent This repo pins agentic-os v0.14.0, which does enforce YAML, but no commit has run since the rule landed on 2026-06-04. The existing tree is uncaught and the next commit will fail `code-comments` until these are cleaned. ## Scope * Already on a YAML-enforcing rev. Bump to v0.16.0 while here. * Clean the violations now, before the next commit fails on them. Top offenders: * `parsers/_registry.yml` - 6 * `parsers/dig.yml` - 6 * `parsers/nc-zv.yml` - 5 * `parsers/ping.yml` - 5 * `parsers/ssh-exec.yml` - 5 * `parsers/tailscale-ping.yml` - 5 ## Done when * the repo pins agentic-os v0.16.0 with `- id: code-comments` active in the managed block * `pre-commit run code-comments --all-files` passes with no `excludes` grandfathering, beyond genuinely generated or vendored paths Cross-repo context: the catalogue was built 2026-06-08. Sibling meta-work is tracked in agentic-os (check changes) and infrastructure (ansible version-sync role).

coilysiren referenced this issue from a commit

2026-06-08 23:54:11 +00:00

chore(code-comments): clean comment-discipline violations; bump agentic-os v0.16.0

coilysiren closed this issue

2026-06-08 23:54:11 +00:00

Commenting is not possible because the repository is archived.