repo-health-sweep

Audits repository skills, docs, conventions, and examples against the current package surface.

1.8k|61|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/HugoRCD/evlog --skill repo-health-sweep
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-health-sweep
Source: https://github.com/HugoRCD/evlog/tree/main/apps/evi/agent/skills/repo-health-sweep
Command: npx skills add https://github.com/HugoRCD/evlog --skill repo-health-sweep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation, skill files, and examples silently drift out of sync with the actual code as a repository evolves, leaving users with stale API references, wrong defaults, and broken examples that erode trust.

Core Features & Use Cases

  • Skills vs Reality Check: Verifies every SKILL.md claim (API names, options, defaults, exports, signatures) against the real package surface on the current main branch.
  • Docs Quality Audit: Detects stale, contradictory, or missing documentation pages, and cross-checks tables of adapters, env vars, and exports against source code.
  • Convention & Example Drift Detection: Enforces repo rules from AGENTS.md (export registration, changeset policy, test placement) and validates that runnable examples match the current API.
  • Use Case: On a bi-weekly schedule, run the sweep over the evlog repository to produce a report of grounded findings, file draft PRs for mechanical fixes, and create Linear issues for decisions.

Quick Start

Ask the agent to run a repo health sweep over the evlog repository and report any skills, docs, or examples that contradict the current package surface.

Frequently Asked Questions about repo-health-sweep

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

FAQPage Schema
How do I audit repository documentation for stale content?

Run the repo health sweep, which checks every docs page against the current source code on main. It flags stale pages, contradictory sibling pages, missing feature docs, and tables listing options or adapters the code does not support.

How to verify skill files match the actual package API?

The sweep compares every API name, option, default, export, and function signature referenced in SKILL.md files against the real package surface. A curried call shown where the API is two-arg, or an option that does not exist, is reported as a finding.

What does the repo health sweep check besides documentation?

It also enforces convention drift rules from AGENTS.md, such as export registration in package.json and tsdown.config.ts, changeset policy, and test placement, plus validates that examples and skeleton directories match the current API.

Does the sweep create pull requests automatically?

Only for mechanical fixes where checks pass and no judgement is needed, with one draft PR per finding after lint, typecheck, and tests pass. Everything else becomes a Linear issue or a proposal in the report, never code shipped on its own initiative.

How are duplicate findings avoided across sweep runs?

Before filing anything, the sweep lists existing Linear issues and searches GitHub for open issues, PRs, or drafts on the same ground, including its own earlier runs. A stale draft gets a rebase and comment rather than a replacement.