feat(code-comments): extend comment discipline to YAML #159

Closed
opened 2026-06-04 09:44:44 +00:00 by coilysiren · 0 comments
Owner

The code-comments validator only scans a fixed set of source extensions and YAML was never among them, so multi-line # comment blocks in playbooks, manifests, and workflows sail through unchecked. YAML comments are #, identical to .py/.sh, so extending the rule is a one-line addition to LINE_COMMENT_PREFIXES.

Scope:

  • Add .yaml/.yml to LINE_COMMENT_PREFIXES in agentic_os/check_code_comments.py.
  • Remove the deliberate infrastructure opt-out in apply-agentic-os-hooks.py so infra becomes the proving ground.
  • Grandfather agentic-os's own pre-existing YAML comment blocks (example/config files) via [tool.agentic-os.code-comments] excludes.

Cleanup of grandfathered YAML and fleet-wide rollout as consumer repos bump the rev is tracked separately.

The `code-comments` validator only scans a fixed set of source extensions and YAML was never among them, so multi-line `#` comment blocks in playbooks, manifests, and workflows sail through unchecked. YAML comments are `#`, identical to `.py`/`.sh`, so extending the rule is a one-line addition to `LINE_COMMENT_PREFIXES`. Scope: - Add `.yaml`/`.yml` to `LINE_COMMENT_PREFIXES` in `agentic_os/check_code_comments.py`. - Remove the deliberate `infrastructure` opt-out in `apply-agentic-os-hooks.py` so infra becomes the proving ground. - Grandfather agentic-os's own pre-existing YAML comment blocks (example/config files) via `[tool.agentic-os.code-comments]` excludes. Cleanup of grandfathered YAML and fleet-wide rollout as consumer repos bump the rev is tracked separately.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
coilyco-flight-deck/agentic-os#159
No description provided.