check-docs

Analyze git commits to identify documentation update needs and affected areas.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/djimontyp/task-tracker --skill check-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-docs
Source: https://github.com/djimontyp/task-tracker/tree/main/.claude/skills-old/check-docs
Command: npx skills add https://github.com/djimontyp/task-tracker --skill check-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents documentation drift by automatically detecting when code changes require corresponding documentation updates, ensuring your project docs stay current and accurate.

Core Features & Use Cases

  • Change Analysis: Analyzes git commits to identify backend and frontend file modifications
  • Documentation Mapping: Automatically maps code changes to relevant documentation files
  • Missing Docs Detection: Identifies documentation gaps and suggests creation of missing files
  • Use Case: After completing a major feature implementation, use this Skill to identify which API documentation, architecture guides, and frontend docs need updating before your PR review.

Quick Start

Use the check-docs skill to analyze the last 5 commits for documentation needs.

Frequently Asked Questions about check-docs

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

FAQPage Schema
How do I detect which documentation needs updating after code changes?

Documentation drift occurs when code changes outpace doc updates. This Skill analyzes git commits touching backend and frontend files, maps changes to affected areas (API routes, models, services, pages, components), and flags documentation that requires updates or is missing entirely.

Can I automatically identify missing documentation from git commits?

Yes. The Skill examines commits in feature, refactor, and task branches, extracts affected code areas, and produces a structured report that lists which documentation files should exist but don't, helping you close documentation gaps before PR review.

How do I keep API and frontend documentation in sync with code?

After completing code changes, run this Skill on recent commits to receive a change-size assessment (small/medium/large) and a mapping of modified files to their corresponding documentation. This prevents architectural guides, API docs, and component documentation from falling out of date.

What does the documentation analysis report include?

The report extracts commit messages, lists affected backend and frontend areas, computes overall change scope, maps code files to documentation files, and identifies missing documentation—giving you a complete checklist of what needs writing or revision.

Does this work with feature branches and refactoring commits?

Yes. The Skill targets commits marked as feature, refactor, or task changes within backend/app and frontend/src directories, making it suitable for analyzing work in progress before merging and ensuring documentation updates are planned alongside code review.