write-app-change-log

Write App Change Log

This skill automates the process of creating a concise and meaningful changelog for the app.

Workflow

1. Fetch Latest Tags:
2. Ensure all tags are fetched from the remote repository.
3. Example: git fetch --tags origin

1. Identify the Base Tag:
2. Find the latest git tag that matches the pattern v*.
3. Example: git tag -l "v*" --sort=-v:refname | head -n 1

1. Collect Commits:
2. Get all commits from the identified tag to the current HEAD.
3. For each commit, collect the title and the full description.
4. Example: git log <base-tag>..HEAD --pretty=format:"%s%n%b%n---"

1. Filter App-Related Commits:
2. Analyze the commit messages and files changed.
3. Exclude commits that primarily affect:
4. Repository infrastructure (e.g., .github/, scripts/, fastlane/ except changelogs).
5. CI/CD pipelines (e.g., workflow YAML files, Dockerfiles).
6. Build tools configuration (unless it directly impacts app behavior).
7. Internal documentation or maintenance (e.g., README.md, AGENTS.md, task.md, implementation_plan.md).
8. Include commits that modify:
9. App source code (app/, database/, network/).
10. Resources (strings.xml, UI layouts).
11. User-facing features or bug fixes.

1. Identify Meaningful Changes:
2. From the filtered list, select the 2-5 most significant changes.
3. Focus on what is most impactful for the end-user (new features, major bug fixes, performance improvements).

1. Match Style and Tone:
2. Read the existing changelogs in fastlane/metadata/android/en-US/changelogs/.
3. Identify the highest numbered file (e.g., 9.txt).
4. Analyze the language, tone, and formatting of recent entries.
5. Maintain the same concise and professional style.
6. 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.

1. Update the Latest Changelog:
2. Take the identified meaningful changes.
3. Draft the new content matching the established style.
4. 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).