skills.rest
Ronin15
Ronin15COMMUNITY
Explore all skills by this author →
GitHub

hammer-changelog-generator

Generate a structured Markdown changelog from SDL3 HammerEngine git history.

14|2|Updated Mar 24, 2025
Search Tags:#automation#changelog#code analysis#documentation#technical writing#release notes#git history
One-click install
npx skills add https://github.com/Ronin15/SDL3_HammerEngine_Template --skill hammer-changelog-generator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hammer-changelog-generator
Source: https://github.com/Ronin15/SDL3_HammerEngine_Template/tree/main/.claude/skills/hammer-changelog-generator
Command: npx skills add https://github.com/Ronin15/SDL3_HammerEngine_Template --skill hammer-changelog-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git.

What problem does it solve?

Manually compiling detailed changelogs from Git history, analyzing code changes, and integrating performance data is a tedious, error-prone process that delays release documentation and consumes valuable developer time.

Core Features & Use Cases

  • Automated Git & File Analysis: Extracts changes from Git history, categorizes modifications by system, and identifies affected functions/classes with line counts.
  • Comprehensive Report Generation: Creates a professionally formatted Markdown changelog including an executive summary, detailed changes, performance analysis, testing summary, and an optional architect review.
  • Integration with Architect & Tests: Can optionally trigger an architectural review by a dedicated agent and run relevant test suites to verify changes, integrating feedback directly into the changelog.
  • Use Case: When preparing for a "World Update #3" release, use this Skill to automatically generate a detailed changelog, including performance impacts, test results, and a summary of architectural changes, saving hours of manual documentation effort.

Quick Start

Generate a changelog for the current branch, focusing on AI system changes, and request a full architectural review.

Frequently Asked Questions about hammer-changelog-generator

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

FAQPage Schema
How do I automatically generate a changelog from git history?▼

Automated changelog generation extracts commits and file changes from git history, categorizes modifications by system, and produces a professionally formatted markdown file. This Skill analyzes your repository to create structured documentation without manual compilation.

Can I include performance analysis and test results in my release notes?▼

Yes. This Skill integrates performance data, threading behavior, architectural review, and test verification directly into the changelog. It produces a comprehensive markdown report that combines code changes with performance impacts and test summaries.

What format does the generated changelog use?▼

The changelog is output as markdown with sections for executive summary, changes overview, detailed changes by system, performance analysis, threading behavior, architecture coherence, and testing summary. The file follows the naming pattern changelogs/CHANGELOG_[UPDATE_NAME].md.

Do I need git installed to use this Skill?▼

Yes. Git is a required dependency. The Skill extracts change history and file modifications directly from your repository, so git must be available in your development environment.

How does this handle multi-domain changes across AI, Collision, Rendering, and Threading systems?▼

The Skill categorizes modifications by system domain, identifies affected functions and classes with line counts, and organizes changes into dedicated sections. It aggregates architectural impacts and threading behavior across all domains into a single coherent report.

What's the difference between manual changelog writing and automated generation?▼

Automated generation eliminates hours of manual documentation by extracting changes directly from git, analyzing code systematically, and integrating performance and test data. Manual writing is error-prone and delays releases; this approach produces consistent, comprehensive documentation at release time.

Related Skills

Explore More Content & Communication Skills→
GolferGeekGolferGeek

Orchestrator Git Standards

Enforce conventional branch names, commit messages, and repository organization for Git workflows.

Community
Basic
frostantfrostant
42

changelog-generator

Converts git commit history into categorized, ready-to-publish markdown release notes.

Community
Intermediate
shredbxshredbx

research-git-patterns

Extract implementation patterns and story context from Git history.

Community
Intermediate
allanninalallanninal
1

changelog-generator

Convert git commits into changelogs following Keep a Changelog and Conventional Commits.

Community
Intermediate