docs-freshness

Detect documentation drift from Rust, Python, and protocol changes.

Updated Feb 12, 2026
One-click install
npx skills add https://github.com/jmduea/emotiv-cortex-rs --skill docs-freshness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-freshness
Source: https://github.com/jmduea/emotiv-cortex-rs/tree/main/.github/skills/docs-freshness
Command: npx skills add https://github.com/jmduea/emotiv-cortex-rs --skill docs-freshness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill detects when source code, protocols, or configuration changes are out of sync with accompanying documentation, preventing outdated READMEs, specifications, and changelogs.

Core Features & Use Cases

  • Change Mapping: Correlates modifications in Rust, Python, and documentation files with required doc updates.
  • Doc Gap Reporting: Generates a list of missing or outdated documentation sections, blocking merges when critical gaps exist.
  • Use Case: After adding a new API endpoint, the skill flags the need to update the changelog and README to reflect the change.

Quick Start

Run the docs-freshness skill to get a list of documentation updates needed after recent code changes.

Frequently Asked Questions about docs-freshness

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

FAQPage Schema
How do I detect documentation drift after modifying Rust or Python code?

Documentation drift is detected by correlating code and protocol modifications with existing documentation files. This analysis identifies missing or outdated sections in READMEs, specs, and changelogs, ensuring public behavior changes are accurately reflected before merging.

How do I ensure my README and changelog stay in sync with new API endpoints?

Keeping your README and changelog in sync requires mapping source code changes to required documentation updates. This flags missing sections and blocks merges until critical documentation gaps are resolved and the changelog accurately reflects the new endpoint.

Can I block pull requests when protocol changes are not reflected in the spec?

Yes, you can block pull requests when protocol changes are not reflected in the spec. By enforcing documentation freshness checks, merges are blocked if critical gaps exist between modified code and the accompanying specification or changelog.

What is the best way to automate required doc updates for protocol modifications?

The best way to automate required doc updates is to run a change mapping process that correlates protocol modifications with documentation files. This generates a gap report of missing or outdated sections, enforcing updates before a merge can occur.

Does documentation drift detection work with both Rust and Python files?

Yes, documentation drift detection works with both Rust and Python files. It analyzes changes across these languages to determine the required updates needed for README, spec, and changelog files to maintain documentation freshness.

When should I run a documentation freshness check?

You should run a documentation freshness check after modifying source code, protocols, or configuration files. This identifies outdated READMEs, specifications, or changelogs and ensures they are updated before the changes are merged.