hyper-docs

Identify and update documentation affected by code changes during the docs phase.

2|1|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/galatanovidiu/hyper7 --skill hyper-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hyper-docs
Source: https://github.com/galatanovidiu/hyper7/tree/main/skills/hyper-docs
Command: npx skills add https://github.com/galatanovidiu/hyper7 --skill hyper-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and update documentation affected by code changes during the docs phase. Applies to README, CHANGELOG, API references, inline docstrings, and architecture docs to ensure consistency across the project. Ensures a docs section is appended to checks.md and records a no-op verdict when no updates are needed.

Core Features & Use Cases

  • Identify documentation touched by a feature change (README, CHANGELOG, API references, inline docstrings, architecture docs) and verify its freshness.
  • Update stale docs and append a docs section to checks.md describing the outcome.
  • Record a no-op verdict with rationale when no updates are necessary.

Quick Start

Run the docs phase to scan affected files and update documentation surfaces in checks.md.

Frequently Asked Questions about hyper-docs

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

FAQPage Schema
How do I automate documentation updates when code changes happen?

Automate documentation updates by running a docs phase that identifies affected files like README, CHANGELOG, and API references, updates stale content, and appends the outcome to checks.md.

How does automatic documentation freshness checking work for project docs?

Documentation freshness checking scans files affected by feature changes, verifies consistency across API references and inline docstrings, and records a no-op verdict in checks.md when no updates are needed.

What is the best way to keep CHANGELOG and architecture docs consistent with code?

To keep CHANGELOG and architecture docs consistent, run a dedicated docs phase to verify freshness, update stale documentation surfaces, and append a docs section to checks.md describing the outcome.

Can I track documentation updates inside my existing checks.md file?

Yes, you can track documentation updates by appending a dedicated docs section to checks.md that describes the outcome, including a no-op verdict when no updates are necessary.

Does this documentation update workflow handle inline docstrings and API references?

Yes, the documentation update workflow handles inline docstrings and API references by scanning affected files during the docs phase and verifying their freshness.

What happens when no documentation updates are needed after a code change?

When no documentation updates are needed, the workflow records a no-op verdict with rationale in the docs section of checks.md.