changelog-audit

Name: changelog-audit
Availability: InStock
Author: thachrocky12345

Generate a changelog audit across branches, commits, and contributors in multiple git repositories.

Updated May 11, 2026

Search Tags:#git #changelog #audit #release notes #contributors #commit log #branch inventory

Ready to run

npx skills add https://github.com/thachrocky12345/local-agent-train-workstation --skill changelog-audit-thachrocky12345

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: changelog-audit
Source: https://github.com/thachrocky12345/local-agent-train-workstation/tree/main/.claude/skills/changelog-audit
Command: npx skills add https://github.com/thachrocky12345/local-agent-train-workstation --skill changelog-audit-thachrocky12345

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Tracking changes across multiple repositories and branches is tedious and error-prone, especially when the same project exists in both primary and submodule locations. This Skill automates the collection of branch inventories, commit logs, contributor activity, and cross-repo sync status into a single structured audit report. ## Core Features & Use Cases - Multi-repo branch inventory: Collects branch lists, commit counts, and last-activity dates from four repo locations (primary and submodule copies of backend and frontend). - Categorized change summary: Groups commits into categories like infrastructure, models and migrations, API, seed data, frontend features, bug fixes, and security. - Cross-repo sync check: Compares HEAD commits between primary and infra copies to detect drift. - Use Case: Before a release, ask for a changelog audit since the last release date to get an executive summary, contributor breakdown, stale branch recommendations, and unmerged work flagged in `Docs/CHANGELOG-AUDIT.md`. ## Quick Start Run a changelog audit across all repos since 2024-01-01 and write the report to Docs/CHANGELOG-AUDIT.md.

Frequently Asked Questions about changelog-audit

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

FAQPage Schema

How do I generate a changelog across all git branches?▼

Use git log --all --oneline --since=<date> to collect commits from every branch, then group them by category such as infrastructure, API, or bug fixes. This Skill automates that collection across four repo locations and writes a structured Markdown report.

How to audit contributor activity in a git repository?▼

Run git log --all --format='%ae' --since=<date> and count unique authors to measure contributor activity. The audit aggregates commits per author across all branches and repositories into a contributor activity section.

Can I compare sync status between a repo and its submodule copy?▼

Yes, compare the HEAD commits of the primary repository and its submodule copy to detect drift. The audit includes a cross-repo sync status section that flags mismatches between primary and infra copies.

What git commands list stale branches that need cleanup?▼

Use git branch -a with creator date and last commit subject to identify branches with no recent activity, then git diff --stat against main to check for unmerged work. The audit's recommendations section highlights stale branches and unmerged changes.

Does the changelog audit work with a date range or commit range?▼

Yes, the audit accepts a since-date or commit reference as its argument to scope the commit log and contributor queries. Without it, commands default to the full history subject to output limits.