Skip to content

chore: add validate-counts job for README aggregate count enforcement#10

Merged
TMHSDigital merged 1 commit intomainfrom
chore/add-validate-counts-job
Apr 26, 2026
Merged

chore: add validate-counts job for README aggregate count enforcement#10
TMHSDigital merged 1 commit intomainfrom
chore/add-validate-counts-job

Conversation

@TMHSDigital
Copy link
Copy Markdown
Owner

Adds validate-counts job per the canonical pattern from CFX/Unity, adapted to use a filesystem walk instead of plugin.json introspection (this repo's plugin.json is glob-based, so len(m['skills']) would always be 1).

The job enforces that README.md aggregate count claims (e.g. "17 skills", "10 rules") match actual on-disk counts. Currently passes; pure CI hardening that catches future drift before it ships.

Complementary to the ecosystem-wide drift-check stale-counts pass (warn-only): this job hard-fails CI on the headline count specifically.

Canary for the 6-repo rollout per TMHSDigital/Developer-Tools-Directory#39. Design doc: dtd39-canonical-pattern.md.

Adds a validate-counts job that enforces README.md aggregate count
claims match the actual filesystem counts of skills/SKILL.md and
rules/*.mdc. Mirrors the canonical pattern shipping in CFX and Unity.

Filesystem walk (not plugin.json introspection) because this repo
uses glob-based plugin.json (`"skills": ["skills/**/SKILL.md"]`),
where len(m['skills']) would always return 1. The walk approach
matches what the existing "Count components" step already does
informationally; this job promotes it to enforcement.

Currently passes (skill/rule counts match README claims). Pure
CI hardening; catches future drift before it ships.

Refs TMHSDigital/Developer-Tools-Directory#39.

Signed-off-by: TMHSDigital <154358121+TMHSDigital@users.noreply.github.com>
Made-with: Cursor
@TMHSDigital TMHSDigital merged commit e6b1c08 into main Apr 26, 2026
11 checks passed
@TMHSDigital TMHSDigital deleted the chore/add-validate-counts-job branch April 26, 2026 02:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant