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

New issue

Closed

opened 2026-06-08 21:50:54 +00:00 by coilysiren · 1 comment

coilysiren commented

2026-06-08 21:50:54 +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 113 latent violations under the current check (v0.16.0): 0 in code, 113 in YAML.

Why these are latent

This repo pins agentic-os v0.11.1, which predates YAML enforcement (landed in v0.14.0 on 2026-06-04). code-comments runs on code today but has never scanned YAML here, so the YAML violations are latent.

Scope

Bump the managed agentic-os rev to v0.16.0.
Clean the YAML violations the upgraded check surfaces.

Top offenders:

deploy/main.yml - 40
.forgejo/workflows/build-publish-deploy.yml - 34
.agents/skills/categories.yaml - 13
.github/workflows/action.yml - 13
.coily/coily.yaml - 10
.pre-commit-config.yaml - 2

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 **113** latent violations under the current check (v0.16.0): 0 in code, 113 in YAML. ## Why these are latent This repo pins agentic-os v0.11.1, which predates YAML enforcement (landed in v0.14.0 on 2026-06-04). `code-comments` runs on code today but has never scanned YAML here, so the YAML violations are latent. ## Scope * Bump the managed agentic-os rev to v0.16.0. * Clean the YAML violations the upgraded check surfaces. Top offenders: * `deploy/main.yml` - 40 * `.forgejo/workflows/build-publish-deploy.yml` - 34 * `.agents/skills/categories.yaml` - 13 * `.github/workflows/action.yml` - 13 * `.coily/coily.yaml` - 10 * `.pre-commit-config.yaml` - 2 ## 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-14 04:53:34 +00:00

chore(code-comments): clean YAML comment-discipline violations

coilysiren added the

label

2026-06-17 07:04:54 +00:00

coilysiren commented

2026-06-17 08:23:29 +00:00

Author

Owner

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: burndown-2026-06.

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: `burndown-2026-06`.

coilysiren

2026-06-17 08:23:30 +00:00