update-official-doc-summary

Generate Markdown changelog summaries from git diffs of documentation snapshots.

Updated May 24, 2026
One-click install
npx skills add https://github.com/empty-can/cc-relative-info --skill update-official-doc-summary
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-official-doc-summary
Source: https://github.com/empty-can/cc-relative-info/tree/main/.claude/skills/update-official-doc-summary
Command: npx skills add https://github.com/empty-can/cc-relative-info --skill update-official-doc-summary

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill removes the repetitive work of manually reviewing changes in official documentation snapshots and turning them into readable update summaries. It helps teams track what changed across llms.txt and llms-full.txt sources without missing important additions, major revisions, or release-note-style announcements.

Core Features & Use Cases

  • Diff-based summary generation: Compares a previous commit against the current repository state and detects changed documentation pages for supported sites.
  • Structured change classification: Separates updates into highlights, newly added pages, major updates, minor updates, and site-specific news sections when available.
  • Dual-output publishing: Produces a detailed narrative version and a lightweight version extracted deterministically from the detailed file.
  • Archive-aware workflow: Preserves prior summaries with dated archive folders and embeds run metadata for the next incremental update.
  • Use Case: Use this Skill when maintaining a repository of official documentation mirrors and you need consistent changelog-style Markdown for Claude Code Docs or MCP updates after each content refresh.

Quick Start

Ask the agent to run the update-official-doc-summary skill for a target site and generate the latest detailed and light summaries from the newest documentation diff.

Frequently Asked Questions about update-official-doc-summary

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

FAQPage Schema
How do I generate Markdown release notes from git diffs of official documentation?

You generate release notes from git diffs by comparing a previous commit against current documentation snapshots and classifying changed pages into structured changelog summaries. This process automatically detects additions and revisions to produce narrative updates.

What is the best way to track llms.txt updates across mirrored documentation repositories?

Tracking llms.txt updates is best handled by applying commit-based diff detection to classify page-level changes into highlights, major updates, and newly added pages. This creates consistent, incremental reports for archival publishing.

Can I create both detailed and lightweight changelog summaries from documentation changes?

Yes, you can create both detailed and lightweight changelog summaries from documentation changes through dual-output publishing. The system generates a detailed narrative version and deterministically extracts a light summary from it.

How do I preserve previous documentation summaries when generating new incremental reports?

You preserve previous documentation summaries by using an archive-aware workflow that stores prior reports in dated folders. This approach embeds run metadata into the new output to maintain continuity for future incremental updates.

Does this changelog generation method support Claude Code Docs and Model Context Protocol updates?

Yes, this changelog generation method supports Claude Code Docs and Model Context Protocol updates. It processes mirrored llms.txt and llms-full.txt snapshots to detect and summarize incremental content changes for these specific sources.