This skill should be used when updating the project CHANGELOG, tracking requirement changes, recording design decisions, or documenting version history. Uses git-diff to detect and categorize changes to both code and requirements. Trigger on "changelog", "version history", "what changed", or after significant commits.
The 'ghe-changelog' skill is designed to automate and streamline the process of managing project changelogs. It helps teams track and document changes to code, design, and requirements by using git-diff to detect and categorize changes between commits. This skill solves the problem of manually tracking what has changed in a project over time, reducing the likelihood of errors in version history, and ensuring that every change is documented appropriately in a standardized format.
The primary features of the 'ghe-changelog' skill include automatic generation of changelog entries based on recent commits, categorization of changes into predefined sections such as 'Added', 'Changed', 'Fixed', 'Requirements', and 'Design', and structured output that aligns with a standard changelog format. It also integrates with version control systems to detect changes in specific directories like 'REQUIREMENTS/' and 'DESIGN'. By using this tool, teams can ensure that changelogs are consistently maintained and reflect all significant updates in the project.
This skill is particularly useful for software development teams that need to maintain detailed and up-to-date version histories. It is intended for users who want to automate the generation of changelogs without manually tracking every change. It is ideal for projects that use Git for version control and follow a structured approach to documenting code changes, requirements, and design decisions.
The ghe-changelog skill uses git-diff to detect changes between commits and categorizes them based on commit messages and affected files. It identifies additions, changes, fixes, design modifications, and requirement updates.
The skill categorizes changes based on several directories, such as 'REQUIREMENTS/' for requirements changes and 'DESIGN' or 'ARCHITECTURE' for design-related changes. These directories must be present in the project for the tool to function correctly.
No, the ghe-changelog skill is designed to work specifically with Git repositories. It relies on git-diff to detect changes between commits and will not function without Git.
The changelog is structured into sections such as 'Added', 'Changed', 'Fixed', 'Requirements', and 'Design'. These sections correspond to different types of changes and are organized under the version number and release date.
If the skill detects an error in the specifications, it will stop immediately and inform the user of the potential issue. It will wait for explicit guidance before proceeding, in accordance with the 'IRON LAW'.
Quick Setup:
.claude/skills/Repository
Emasoft/ghe-marketplace