skills.rest
Data-Wise
Data-WiseCOMMUNITY
Explore all skills by this author →
GitHub

doc-classifier

Classify documentation requirements from code changes and commit ranges.

7|Updated Dec 23, 2025
Search Tags:#automation#git#developer tools#code review#documentation#classification
One-click install
npx skills add https://github.com/Data-Wise/claude-plugins --skill doc-classifier-data-wise
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doc-classifier
Source: https://github.com/Data-Wise/claude-plugins/tree/main/craft/skills/docs/doc-classifier
Command: npx skills add https://github.com/Data-Wise/claude-plugins --skill doc-classifier-data-wise

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of determining what types of documentation are necessary for code changes, saving developers time and ensuring comprehensive documentation.

Core Features & Use Cases

  • Automated Documentation Assessment: Analyzes code changes, commit history, and feature scope to predict documentation requirements.
  • Structured Output: Provides clear classification data indicating which documentation types (guide, refcard, gif_demo, mermaid) are needed and why.
  • Use Case: After a developer commits changes to a new module with several new commands, this Skill can automatically identify that a new user guide, a quick reference card, and a demonstration GIF are required.

Quick Start

Use the doc-classifier skill to analyze documentation needs for the 'session tracking' feature.

Frequently Asked Questions about doc-classifier

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

FAQPage Schema
How do I determine what documentation to write for new code changes?▼

Automated documentation assessment analyzes code changes, commit history, and feature scope to predict requirements. It outputs structured classifications indicating required documentation types like guides, refcards, GIF demos, and Mermaid diagrams.

How does commit history analysis classify documentation requirements?▼

Commit history analysis classifies documentation requirements by evaluating feature scope alongside new commands, modules, and hooks. It determines the priority of guides, refcards, GIF demos, and Mermaid diagrams based on workflow complexity.

Can I automate the generation of Mermaid diagrams and GIF demos after classifying documentation needs?▼

Yes, you can automate generation by using the structured classification output from this analysis. It integrates with other documentation crafting skills to automatically generate and validate the required guides, refcards, GIF demos, and Mermaid diagrams.

Does the documentation classifier work with Git commit ranges for code review?▼

Yes, the documentation classifier works with Git commit ranges during code review. It analyzes code changes within specified commit ranges to identify necessary user guides, reference cards, and visual demonstrations.

What types of documentation does the code change analysis output?▼

The code change analysis outputs structured classification data for four main documentation types: guides, refcards, gif_demo, and mermaid diagrams. It specifies which types are needed and explains why based on the workflow complexity.

Related Skills

Explore More Software Engineering Skills→
mcauduro0mcauduro0
1

requesting-code-review

Dispatch a subagent to analyze code changes against requirements and quality standards.

Community
Intermediate
DocaariDocaari
1

system-architect

Generate versioned Mermaid architecture diagrams and ADRs from approved specs.

Community
Advanced
compartmentdevcompartmentdev
229

public-docs-maintenance

Align public documentation with material changes in Compartment workflows.

Official
Intermediate
ather-techieather-techie
6

commit-message

Generate standardized git commit messages from staged changes and repository history.

Community
Intermediate