skills.rest
Avihai-H
Avihai-HCOMMUNITY
Explore all skills by this author →
GitHub

count-registry

Validate entity count consistency between code and documentation using a manifest file.

Updated Apr 19, 2026
Search Tags:#project management#github#statistics#code consistency#automated counting
One-click install
npx skills add https://github.com/Avihai-H/infraops --skill count-registry-avihai-h
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: count-registry
Source: https://github.com/Avihai-H/infraops/tree/main/.github/skills/count-registry
Command: npx skills add https://github.com/Avihai-H/infraops --skill count-registry-avihai-h

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a centralized source for accurate counts of project entities such as agents, skills, instructions, and validators. It ensures that entity quantities remain consistent with reality by auto-computing counts and preventing hardcoded values.

Core Features & Use Cases

  • Canonical Counts: Centralized and auto-computed counts of all relevant project entities.
  • Descriptive Phrasing: Offers a guideline for referring to entity counts to maintain clarity.
  • No Hardcoding: Enforces non-hardcoding of counts in the documentation for accurate reflection of project reality.

Quick Start

View and refer to counts using the '.github/count-manifest.json' file or refer to the skill as a reference within the documentation.

Frequently Asked Questions about count-registry

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I ensure entity count consistency between code and documentation in a GitHub repository?▼

To ensure entity count consistency, you can validate counts using a manifest file to auto-compute project statistics and prevent manual discrepancies. This approach eliminates hardcoded values by referencing a centralized count source.

What is the best way to prevent hardcoded entity quantities in project reporting?▼

Preventing hardcoded entity quantities is achieved by enforcing non-hardcoding rules and utilizing a canonical count manifest file. This provides a centralized source for accurate counts of agents, skills, and validators.

How do I validate project state counts using JSON file parsing for infrastructure management?▼

You validate project state counts by parsing a JSON manifest file to compare documented entities against actual repository conditions. This ensures infrastructure management reporting accurately reflects the current project state.

Does this automated counting approach work without external dependencies?▼

Yes, this automated counting approach works without external dependencies. It relies solely on parsing a JSON manifest file within your repository to enforce code consistency and auto-compute entity statistics.

When do I need a centralized manifest file for project statistics?▼

You need a centralized manifest file for project statistics when maintaining multiple project entities like agents, skills, and validators. It offers a guideline for referring to entity counts to maintain clarity and prevent documentation drift.

Related Skills

Explore More Software Engineering Skills→
fxckcodefxckcode

git-setup-skill

Automate Git/GitHub repository setup with baseline governance files and CI workflows.

Community
Advanced
jurislmjurislm

codebase-sync

Audit and refresh README.md and CLAUDE.md to match the current codebase.

Official
Intermediate
juanca202juanca202

speckit-git-commit

Automate Git commits after Spec Kit command events.

Community
Basic
gesmith0606gesmith0606

gsd-list-workspaces

Scan GSD workspace manifests and summarize status in a table.

Community
Intermediate