skill-staleness-check

To automatically update stale documentation, this skill reads webhook payloads to match changed files to skill sources and generates pull requests for updated SKILL.md files. It detects upstream changes and selectively regenerates only the affected skill sections.

Automated staleness detection works by reading webhook payloads from TanStack package repositories, matching changed files against defined skill sources, and triggering regeneration workflows to keep skill metadata current. It tracks staleness through governance metrics.

Yes, you need the skill-generate and skill-tree-generator tools to run staleness checks. The skill requires these dependencies to perform selective regeneration of affected sections and coordinate controlled regeneration using cross-skill references.

Yes, you can selectively regenerate specific sections of a stale skill. The staleness check identifies affected skills from upstream changes and uses the skill-generate tool to update only the necessary skill metadata and guidance.

The best way to automate pull requests for outdated skill metadata is triggering a staleness check workflow. It identifies outdated skills by diffing upstream changes, applies frontmatter metadata, and orchestrates PRs for updated SKILL.md files.

A skill becomes stale after upstream docs and code changes when the source files it references are modified. The staleness check matches these changed files to skill sources using frontmatter metadata and flags the skill for regeneration.