stevesolun/ctx / skills/repo-stats-autoupdate
repo-stats-autoupdate
VerifiedKeeps README badge + inline counts in sync with the real number of skills, agents, graph nodes/edges, communities, converted pipelines, and test inventory. Runs automatically on every commit via a git pre-commit hook. Use when the README drifts from reality or before publishing a release.
repo-stats-autoupdate
What this skill does
Reads the authoritative sources for the ctx repo's key numbers and patches README.md in place so badges and inline counts never drift:
| Number | Source of truth |
|---|---|
| Skills | ~/.claude/skill-wiki/graphify-out/graph.json — count nodes where type == "skill" |
| Agents | same file — count nodes where type == "agent" |
| Graph nodes | len(graph["nodes"]) |
| Graph edges | len(graph["edges"]), formatted as 642K / 1.2M |
| Communities | graph/communities.json → total_communities |
| Converted pipelines | ~/.claude/skill-wiki/converted/ subdir count |
| Tests | checked-in README/docs inventory by default; set CTX_UPDATE_REPO_STATS_LIVE_TESTS=1 to refresh from pytest --collect-only -q |
Fields that can't be resolved (e.g. wiki not deployed) are left untouched — the updater never blocks a commit.
How to use it
One-time install (per clone):
git config core.hooksPath .githooks
After that, every git commit runs .githooks/pre-commit which calls the updater and re-stages README.md if any number drifted.
Manual run:
python src/update_repo_stats.py # patch README
python src/update_repo_stats.py --check # exit 1 if stale (for CI)
CTX_UPDATE_REPO_STATS_LIVE_TESTS=1 python src/update_repo_stats.py # refresh test inventory
When NOT to use it
- When you've deliberately phrased a number descriptively (e.g. "over 1,700 skills") — the regex patterns only match exact digits, so prose phrasings are safe, but double-check after big imports.
- When the wiki isn't deployed locally. The updater degrades gracefully: it prints a warning and skips fields it can't resolve. It does not invent numbers.
Known gaps (intentionally out of scope)
- Does not rebuild the graph or wiki. Rebuilding
graph/wiki-graph.tar.gztakes minutes and churns a large artifact — too heavy for per-commit. Runctx-wiki-graphify, thenpython src/validate_graph_artifacts.py --deep, and repack the tarball manually when the skill catalog changes materially. - Does not verify graph integrity. If
graphify-out/graph.jsonis corrupt, you'll get junk numbers. Run the wiki health check (python src/wiki_orchestrator.py --check) separately.
Related files
- src/update_repo_stats.py — the worker
- .githooks/pre-commit — the per-commit trigger
README.md— the target being kept in sync
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |