write-app-change-log
Generates and updates the latest app changelog based on git history since the last version tag.
Best use case
write-app-change-log is best used when you need a repeatable AI agent workflow instead of a one-off prompt. It is especially useful for teams working in multi. Generates and updates the latest app changelog based on git history since the last version tag.
Generates and updates the latest app changelog based on git history since the last version tag.
Users should expect a more consistent workflow output, faster repeated execution, and less time spent rewriting prompts from scratch.
Practical example
Example input
Use the "write-app-change-log" skill to help with this workflow task. Context: Generates and updates the latest app changelog based on git history since the last version tag.
Example output
A structured workflow result with clearer steps, more consistent formatting, and an output that is easier to reuse in the next run.
When to use this skill
- Use this skill when you want a reusable workflow rather than writing the same prompt again and again.
When not to use this skill
- Do not use this when you only need a one-off answer and do not need a reusable workflow.
- Do not use it if you cannot install or maintain the related files, repository context, or supporting tools.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/write-app-change-log/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How write-app-change-log Compares
| Feature / Agent | write-app-change-log | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Generates and updates the latest app changelog based on git history since the last version tag.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Write App Change Log
This skill automates the process of creating a concise and meaningful changelog for the app.
## Workflow
1. **Fetch Latest Tags**:
* Ensure all tags are fetched from the remote repository.
* Example: `git fetch --tags origin`
2. **Identify the Base Tag**:
* Find the latest git tag that matches the pattern `v*`.
* Example: `git tag -l "v*" --sort=-v:refname | head -n 1`
3. **Collect Commits**:
* Get all commits from the identified tag to the current `HEAD`.
* For each commit, collect the title and the full description.
* Example: `git log <base-tag>..HEAD --pretty=format:"%s%n%b%n---"`
4. **Filter App-Related Commits**:
* Analyze the commit messages and files changed.
* **Exclude** commits that primarily affect:
* Repository infrastructure (e.g., `.github/`, `scripts/`, `fastlane/` except changelogs).
* CI/CD pipelines (e.g., workflow YAML files, Dockerfiles).
* Build tools configuration (unless it directly impacts app behavior).
* Internal documentation or maintenance (e.g., `README.md`, `AGENTS.md`, `task.md`, `implementation_plan.md`).
* **Include** commits that modify:
* App source code (`app/`, `database/`, `network/`).
* Resources (`strings.xml`, UI layouts).
* User-facing features or bug fixes.
5. **Identify Meaningful Changes**:
* From the filtered list, select the **2-5 most significant** changes.
* Focus on what is most impactful for the end-user (new features, major bug fixes, performance improvements).
6. **Match Style and Tone**:
* Read the existing changelogs in `fastlane/metadata/android/en-US/changelogs/`.
* Identify the highest numbered file (e.g., `9.txt`).
* Analyze the language, tone, and formatting of recent entries.
* Maintain the same concise and professional style.
* Usually, the format is: `Welcome to Janus <version-name> (<version-code>)` followed by bullet points if multiple changes are listed, or a single descriptive sentence.
7. **Update the Latest Changelog**:
* Take the identified meaningful changes.
* Draft the new content matching the established style.
* **Update** the highest numbered file in `fastlane/metadata/android/en-US/changelogs/` with the new content.
## Guidelines
- Be concise.
- Focus on user value.
- Avoid technical jargon unless necessary.
- Ensure the version name and code in the changelog match the current project state (can be found in `app/build.gradle.kts` or similar).Related Skills
req-change-workflow
Standardize requirement/feature changes in an existing codebase (especially Chrome extensions) by turning "改需求/需求变更/调整交互/改功能/重构流程" into a repeatable loop: clarify acceptance criteria, confirm current behavior from code, assess impact/risk, design the new logic, implement with small diffs, run a fixed regression checklist, and update docs/decision log. Use when the user feels the change process is chaotic, when edits tend to sprawl across files, or when changes touch manifest/service worker/OAuth/storage/UI and need reliable verification + rollback planning.
prd-doc-writer
Write and iteratively refine PRD/需求文档 with a story-driven structure and strict staged confirmations (journey map alignment, per-story single-point confirmation, final generation gate). Use when the user asks to 梳理/撰写/完善 PRD、需求文档、用户故事、验收标准，并希望用 ASCII 线框图与 Mermaid（流程图/状态图/时序图）来减少歧义、共同完成文档。
svelte-code-writer
CLI tools for Svelte 5 documentation lookup and code analysis. MUST be used whenever creating, editing or analyzing any Svelte component (.svelte) or Svelte module (.svelte.ts/.svelte.js). If possible, this skill should be executed within the svelte-file-editor agent for optimal results.
changelog-maintenance
Maintain a clear and informative changelog for software releases. Use when documenting version changes, tracking features, or communicating updates to users. Handles semantic versioning, changelog formats, and release notes.
writer
Document creation, format conversion (ODT/DOCX/PDF), mail merge, and automation with LibreOffice Writer.
wiki-page-writer
Generates rich technical documentation pages with dark-mode Mermaid diagrams, source code citations, and first-principles depth. Use when writing documentation, generating wiki pages, creating technical deep-dives, or documenting specific components or systems.
wiki-changelog
Analyzes git commit history and generates structured changelogs categorized by change type. Use when the user asks about recent changes, wants a changelog, or needs to understand what changed in the repository.
seo-content-writer
Writes SEO-optimized content based on provided keywords and topic briefs. Creates engaging, comprehensive content following best practices. Use PROACTIVELY for content creation tasks.
changelog-automation
Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.
typescript-write
Write TypeScript and JavaScript code following Metabase coding standards and best practices. Use when developing or refactoring TypeScript/JavaScript code.
docs-write
Write documentation following Metabase's conversational, clear, and user-focused style. Use when creating or editing documentation files (markdown, MDX, etc.).
clojure-write
Guide Clojure and ClojureScript development using REPL-driven workflow, coding conventions, and best practices. Use when writing, developing, or refactoring Clojure/ClojureScript code.