How do I install the Repo Stats Autoupdate skill?

Run npx skillmds@latest add stevesolun/repo-stats-autoupdate in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Repo Stats Autoupdate safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Repo Stats Autoupdate?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Repo Stats Autoupdate free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Repo Stats Autoupdate?

stevesolun (@stevesolun) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Repo Stats Autoupdate by stevesolun

Name: Repo Stats Autoupdate
Author: stevesolun

Repo Stats Autoupdate

Keeps 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.

stevesolun Updated Sep 17, 2026

File contents

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.gz takes minutes and churns a large artifact — too heavy for per-commit. Run ctx-wiki-graphify, then python 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.json is 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

---name: repo-stats-autoupdatedescription: Keeps 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 doesReads 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):**```bashgit 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:**```bashpython src/update_repo_stats.py # patch READMEpython 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.gz` takes minutes and churns a large artifact — too heavy for per-commit. Run `ctx-wiki-graphify`, then `python 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.json` is 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](../../src/update_repo_stats.py) — the worker- [.githooks/pre-commit](../../.githooks/pre-commit) — the per-commit trigger- `README.md` — the target being kept in sync

Frequently asked questions