# Write App Changelogs from Git History

Release notes often miss the app changes users care about. This skill reviews Git history, follows existing Fastlane style, and updates the latest changelog.

## Install

```bash
npx skillstore add anysoftkeyboard/write-app-change-log
```

## Metadata

- Status: approved
- Slug: anysoftkeyboard-write-app-change-log
- Skillstore revision: r2
- Version status: missing
- Tree hash: 7e1d0f2ea8b60755b4672d52bd630b8f1f07634a2266a55e6c14d4dd1ff17cb6
- Author: AnySoftKeyboard
- GitHub username: AnySoftKeyboard
- License: MIT
- Repository: https://github.com/AnySoftKeyboard/janus/tree/main/.claude/skills/write-app-change-log
- Ref: 89edfdc710d0846129dcee6a929477b04f08052c
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/anysoftkeyboard-write-app-change-log
- Manifest: https://skillstore.pages.dev/api/skills/anysoftkeyboard-write-app-change-log/manifest

## Capabilities

- Fetches remote Git tags and identifies the latest tag matching v\*.
- Collects commit titles and descriptions between the latest version tag and HEAD.
- Filters infrastructure, pipeline, build configuration, and internal documentation changes.
- Selects two to five significant user-facing features, fixes, or performance improvements.
- Matches recent Fastlane changelog style and updates the highest-numbered changelog file.

## Use Cases

- Prepare a Mobile Release: Create concise release notes from app commits since the latest version tag.
- Summarize Sprint Changes: Separate user-facing improvements from repository maintenance before publishing a build.
- Standardize Store Notes: Match new changelog text to the tone and format of recent Fastlane entries.

## Prompt Templates

### Draft the Latest Changelog

```
Review commits since the latest v* tag. Draft a concise changelog with the most important user-facing changes.
```

### Match Existing Release Style

```
Read recent Fastlane en-US changelogs, review commits since the latest v* tag, and draft the next entry in the same style.
```

### Focus on User Impact

```
Analyze changed files and commit messages since the latest version tag. Exclude maintenance work and select two to five user-visible improvements.
```

### Audit and Update the Changelog

```
Verify the current version name and code, compare recent changelog style, summarize meaningful app changes, and update the highest-numbered Fastlane changelog file.
```

## Limitations

- Requires a Git repository with accessible tags and an origin remote.
- Assumes changelogs use the Fastlane Android en-US directory structure.
- Updates the highest-numbered changelog file instead of creating a new file.
- Output quality depends on clear commit messages and accurate project version metadata.

## Best Practices

- Review the selected commits and version details before publishing the changelog.
- Keep entries concise and describe benefits in language users understand.
- Confirm the destination file is the intended changelog for the current release.

## Anti Patterns

- Do not include CI, documentation, or build maintenance without direct user impact.
- Do not copy technical commit messages directly into store-facing release notes.
- Do not overwrite a changelog until the version name, version code, and target file are verified.

## Security Audit

- Audited at: 2026-07-23T05:01:44.444\+00:00
- Summary: All 15 alerts are false positives caused by Markdown inline code, fixed Git examples, file paths, or ordinary prose. The reviewed instructions contain no command injection, malicious intent, prompt injection, or system reconnaissance.

## Stats

- Views: 221
- Downloads: 8
- Favorites: 0
- Popularity score: 0