skills.rest
SeventeenthEarth
SeventeenthEarthCOMMUNITY
Explore all skills by this author →
GitHub

17th-doc-checker

Analyze code changes to identify documentation updates across docs and contracts.

Updated Jan 23, 2026
Search Tags:#documentation#docs#PR review#analyze#TASK.md#documentation updates
One-click install
npx skills add https://github.com/SeventeenthEarth/glm-worker-mcp --skill 17th-doc-checker
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: 17th-doc-checker
Source: https://github.com/SeventeenthEarth/glm-worker-mcp/tree/main/skills/17th-doc-checker
Command: npx skills add https://github.com/SeventeenthEarth/glm-worker-mcp --skill 17th-doc-checker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill analyzes code changes to identify documentation updates and helps ensure documentation stays aligned with implemented features.

Core Features & Use Cases

  • Documentation impact detection: scans modified files to surface documentation areas (docs/, TASK.md, ADRs) that require updates.
  • PR preparation: generates concise suggested changes for PR reviews and quick edits.
  • Audit workflow: supports branch workflows to verify documentation consistency before releases and after merges.

Quick Start

Run the doc checker on the current branch to identify outdated or missing docs. Use the --staged option to focus on staged changes. Review and apply the suggested updates with your editor or integrated tool.

Frequently Asked Questions about 17th-doc-checker

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

FAQPage Schema
How do I check documentation updates needed after code changes in a PR?▼

To check documentation updates after code changes, scan modified files to surface areas like docs/, TASK.md, and ADRs that require updates. The doc checker identifies outdated or missing docs on your branch and generates suggested changes for PR review.

What is documentation impact detection in TASK-driven development?▼

Documentation impact detection scans modified files to surface documentation areas including docs/, TASK.md, and architecture notes that require updates. It ensures documentation stays aligned with implemented features during TASK-driven development workflows and release checks.

How do I audit docs consistency before releases after merging branches?▼

To audit docs consistency before releases, run the doc checker on your branch to verify documentation alignment after merges. It supports branch workflows to identify outdated or missing docs and provides suggested updates for quick edits before release.

Can I focus documentation analysis on staged changes only?▼

Yes, you can focus documentation analysis on staged changes by using the --staged option. This restricts the doc checker to scan only staged files, helping you review and apply suggested documentation updates specifically for your current commit preparation.

Does the doc checker require specific frontmatter in SKILL.md?▼

Yes, the doc checker requires YAML frontmatter with name and description fields in SKILL.md. It may also reference optional scripts/, references/, or assets/ directories for extended analysis during documentation impact detection and PR reviews.

Related Skills

Explore More Content & Communication Skills→
Codcyber101Codcyber101

skill-creator

Scaffold new Skill units with standardized SKILL.md frontmatter and resource directories.

Community
Basic
ogprotegeogprotege

repo-doc-auditor

Audit repository documentation against code and recent changes.

Community
Advanced
RyderFreeman4LogosRyderFreeman4Logos
12

csa-doc-writing

Provide documentation guidelines for APIs, READMEs, ADRs, and changelogs.

Community
Intermediate
Bang-ismeBang-isme
6

codex-docs-change-sync

Map code diffs to impacted documentation files with confidence scores.

Community
Intermediate