# Generate GitHub Changelogs from Project Changes

Teams need changelogs that reflect code, requirements, and design changes. This skill guides Claude, Codex, and Claude Code through git-based changelog updates.

## Install

```bash
npx skillstore add emasoft/ghe-changelog
```

## Metadata

- Status: approved
- Slug: emasoft-ghe-changelog
- Skillstore revision: r1
- Version status: missing
- Tree hash: 95732ef589d2c7f8c2d5d71f39702e2751549f41040dc6755454cff81129e26c
- Author: Emasoft
- GitHub username: Emasoft
- License: MIT
- Repository: https://github.com/Emasoft/ghe-marketplace/tree/main/plugins/ghe/skills/ghe-changelog
- Ref: 72d5025b022c77f7a51bdf5c1637c689c80e89d1
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, filesystem
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/emasoft-ghe-changelog
- Manifest: https://skillstore.pages.dev/api/skills/emasoft-ghe-changelog/manifest

## Capabilities

- Detects commits since the latest git tag for changelog drafting.
- Categorizes changes into added, changed, fixed, requirements, and design sections.
- Summarizes requirement file additions, updates, deprecations, and version changes.
- Identifies design-impacting changes in architecture, ADR, README, and interface files.
- Provides release workflow guidance for updating CHANGELOG.md, commits, and tags.

## Use Cases

- Prepare Release Notes: Turn recent commits into a structured changelog before a version release.
- Track Requirement Changes: Document new, updated, and deprecated requirement files in the project changelog.
- Review Design Impact: Find architecture and interface changes that should be explained in release documentation.

## Prompt Templates

### Draft Basic Changelog

```
Use ghe-changelog to summarize changes since the last tag and draft an Unreleased changelog section.
```

### Review Requirement Updates

```
Use ghe-changelog to compare requirement files since the last release and list new, updated, and deprecated requirements.
```

### Audit Design Changes

```
Use ghe-changelog to identify design-impacting changes and suggest changelog entries that explain the impact.
```

### Prepare Release Entry

```
Use ghe-changelog to prepare a release changelog for version X.Y.Z, but ask before editing files, committing, tagging, or posting externally.
```

## Limitations

- Requires a git repository with meaningful commit history and tags.
- Examples assume a Unix shell and common command-line tools.
- Generated entries need manual review before release publication.
- GitHub issue integration requires an authenticated GitHub CLI setup.

## Best Practices

- Review generated changelog text before committing or publishing it.
- Use consistent commit messages so categories are accurate.
- Ask for confirmation before writing files, creating tags, or posting to GitHub.

## Anti Patterns

- Do not publish full reports externally without explicit user approval.
- Do not treat generated changelog entries as release-ready without review.
- Do not run shell snippets in repositories that contain untrusted file names or tags.

## Security Audit

- Audited at: 2026-07-06T12:17:09.045\+00:00
- Summary: The skill contains legitimate changelog automation, but it directs agents to run shell, git, and GitHub CLI commands and to write project files. The most serious concerns are the prompt-injection-style absolute instruction language, mandatory external report posting, and permission to write ~/.claude configuration.

## Stats

- Views: 278
- Downloads: 9
- Favorites: 0
- Popularity score: 0