Docs Updater

This one automates the tedious part of release prep by diffing your current branch against the last git tag, then updating your README, CHANGELOG, and any docs folders it finds. It follows Keep a Changelog conventions and tries to categorize commits into Added, Changed, Fixed sections automatically. Useful before cutting a release or opening a PR when you know the docs are stale but don't want to manually review dozens of commits. The workflow is interactive, it shows you what it plans to change and waits for approval before touching anything. Requires at least one git tag to work, since it needs a baseline to compare against.

skills.sh installs: 3.7K
GitHub stars: 369
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add giuseppe-trisciuoglio/developer-kit --skill docs-updater --agent claude-code

Installs into .claude/skills of the current project.

Files

Universal Documentation Updater

Analyzes git changes since the latest release tag and updates the documentation files that should change with them.

Overview

Use git history to identify release-relevant changes, then update README.md, CHANGELOG.md, and any relevant documentation folders. Keep the workflow focused on explicit user approval, precise edits, and repository-specific documentation structure.

When to Use

Use this skill when:

Preparing release notes or an Unreleased changelog update
Syncing README.md or documentation after feature work lands
Reviewing what changed since the last release before a PR or release

Prerequisites

Before starting, verify that the following conditions are met:

# Verify we're in a git repository
git rev-parse --git-dir

# Check that git tags exist
git tag --list | head -5

# Verify documentation files exist
test -f README.md || echo "README.md not found"
test -f CHANGELOG.md || echo "CHANGELOG.md not found"

If no tags exist, inform the user that this skill requires at least one release tag to compare against.