check-feature-docs

Audits git repository changes to ensure documentation files are updated.

6|3|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/ather-techie/SlateFlow --skill check-feature-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-feature-docs
Source: https://github.com/ather-techie/SlateFlow/tree/main/.claude/skills/check-feature-docs
Command: npx skills add https://github.com/ather-techie/SlateFlow --skill check-feature-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents documentation drift by ensuring that every new feature implementation is accompanied by the necessary updates to the project's core documentation files.

Core Features & Use Cases

  • Automated Audit: Scans recent git commits to verify if README.md, ROADMAP.md, and CLAUDE.md were updated alongside code changes.
  • Gap Identification: Highlights exactly which documentation files are missing updates based on the scope of code changes.
  • Use Case: After implementing a new API endpoint, run this skill to confirm you have correctly updated the feature list, roadmap status, and internal architecture conventions.

Quick Start

Run the check-feature-docs skill to audit your current branch and identify missing documentation updates.

Frequently Asked Questions about check-feature-docs

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

FAQPage Schema
How do I check if my git branch has the required documentation updates?

To check git branch documentation updates, this skill audits recent commits and compares branch diffs against mandatory project files like README.md, ROADMAP.md, and CLAUDE.md to identify any missing updates. It highlights exactly which files need synchronization with your code changes.

What is documentation drift and how do I prevent it in my repository?

Documentation drift occurs when feature code is modified without updating project docs. This skill prevents it by enforcing documentation standards, validating that README.md, ROADMAP.md, and CLAUDE.md are updated whenever functional code changes are committed to your git branch.

How do I enforce documentation compliance for new features automatically?

To enforce documentation compliance for new features, this skill scans recent git commits to verify that mandatory project files were modified alongside code changes. It identifies gaps by comparing branch diffs against required documentation files.

Can I audit my git repository to ensure README and ROADMAP files are updated?

Yes, you can audit your git repository to ensure README.md and ROADMAP.md are updated. The skill scans recent commits and validates synchronization between feature code and project documentation, highlighting exactly which mandatory files are missing updates.

Do I need to configure specific files for documentation auditing?

No configuration is needed for documentation auditing. The skill automatically targets README.md, ROADMAP.md, and CLAUDE.md by default, comparing your branch diffs against these mandatory project files to enforce documentation standards without requiring additional setup.

What happens if I modify code but forget to update CLAUDE.md?

If you modify code but forget to update CLAUDE.md, the skill identifies this gap during the audit. It compares your branch diffs against mandatory project files and highlights exactly which documentation files are missing updates based on the scope of your code changes.