update

Crawl upstream docs, regenerate SKILL.md files, and publish plugin versions.

1|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/hlibkoval/claudemd --skill update-hlibkoval
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update
Source: https://github.com/hlibkoval/claudemd/tree/main/.claude/skills/update
Command: npx skills add https://github.com/hlibkoval/claudemd --skill update-hlibkoval

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the maintenance cycle for Claude Code docs by crawling upstream references, regenerating skill entries, bumping versions, and pushing changes.

Core Features & Use Cases

  • Crawl upstream docs to detect changes and refresh references.
  • Regenerate changed SKILL.md files according to project conventions.
  • Update version fields in plugin.json and marketplace.json and generate a changelog entry.
  • Commit and push changes automatically with an integrated changelog.

Quick Start

Run the update workflow to synchronize docs and publish a new version.

Frequently Asked Questions about update

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

FAQPage Schema
How do I automate documentation updates and version bumps for Claude Code plugins?

Automate documentation updates and version bumps by crawling upstream docs, regenerating changed SKILL.md files, syncing version fields in plugin.json and marketplace.json, and committing changes. This workflow handles the end-to-end maintenance cycle automatically.

How does crawling upstream docs detect changes for skill entry regeneration?

Crawling upstream docs detects changes by comparing references against the current repository state, identifying differences, and regenerating changed SKILL.md files via a general-purpose agent to ensure entries match project conventions.

Can I automatically generate a changelog and sync version fields across plugin.json and marketplace.json?

Yes, you can sync version fields across plugin.json and marketplace.json and generate a changelog entry automatically. The workflow updates version numbers and integrates the changelog entry before committing and pushing changes.

What is the best way to commit and push doc changes with an integrated changelog?

The best way to commit and push doc changes is through an automated workflow that regenerates skill entries, updates version fields, generates a changelog entry, and commits and pushes the changes automatically in deterministic steps.

Does this doc maintenance workflow require external dependencies or plugins?

No, this doc maintenance workflow operates without external dependencies or plugins. It implements deterministic steps including crawling, regenerating, updating changelogs, syncing versions, and pushing changes natively.

Why do my regenerated SKILL.md files need to follow project conventions during doc updates?

Regenerated SKILL.md files must follow project conventions to maintain consistency across the documentation maintenance cycle. The regeneration process uses a general-purpose agent to ensure entries align with the established repository standards.