skills/ HoangNguyen0403/agent-skills-standard

common-store-changelog

Generate user-facing release notes for the App Store and Google Play from git history (App Store <=4000 chars, Google Play <=500). Use when generating release notes, app store changelog, play store release, or \"what's new\" text for a mobile app.

0
Installs
—
Rating
—
Success rate
3
Files scanned
Scan passedmobile
Source on GitHub

Security scan

Scan passed

No risky patterns were found in the scanned files.

3 files scannedscanner v1.2.0Oct 11, 2026

Content sha256 afb8187428226a5f… — run codexguild_scan_skills after installing to verify your local copy.

Static analysis is a first line of defense, not a guarantee. Read the source

SKILL.md

exact scanned copy

Store Changelog Standard

Priority: P1 (HIGH)

Always-Apply Rules

  • Character limits: App Store ≤ 4000 chars. Google Play ≤ 500 chars — validate before output.
  • Benefit language: Write what user gains, not what code changed. "Faster checkout" not "refactored cart service".
  • Bullet-only format: One sentence per bullet. No paragraphs. No headers inside notes.
  • Drop internal commits: Exclude chore, refactor, ci, build, test, dependency bumps, and config changes — no user impact.
  • Suppress internal SDK changes: Never mention an analytics or other internal SDK update in store notes; omit it silently rather than explaining the omission.
  • Deduplicate: Merge commits touching same feature into one bullet.

Workflow

  1. Collect: Run git log <last-tag>..HEAD --oneline (or use provided commit list). If no tag exists, use full history.
  2. Triage: Scan commits and touched files. Group by theme: New, Improved, Fixed. Drop internal-only.
  3. Draft — App Store: Write 5–10 benefit-focused bullets, including user-facing changes such as onboarding when present. Optional What's New in [Version] header.
  4. Draft — Google Play: Compress App Store draft to ≤ 500 chars. Prioritise top 3–5 user-facing changes.
  5. Validate: Count characters per store. Check every bullet maps to real commit. Remove jargon.

See Commit-to-Bullet Examples for mapping patterns.

Output Format

App Store (≤ 4000 chars):

What's New in Version X.Y
• [New] <user benefit — one sentence>
• [Improved] <user benefit — one sentence>
• [Fixed] <user benefit — one sentence>

Google Play (≤ 500 chars):

• <highest-impact change>
• <second change>
• <third change>
[Bug fixes and performance improvements.]

Anti-Patterns

  • No jargon: Never use refactor, migrated, deprecated, PR, hotfix, or internal ticket IDs.
  • No chore bullets: chore: upgrade Gradle → drop entirely, never paraphrase as user feature.
  • No bundled bullets: "Fixed login and improved search and added dark mode" → three separate bullets.
  • No character overrun: Validate Play Store notes ≤ 500 chars before returning — truncate + rewrite if needed.
  • Three-bullet Play rule: When the input names exactly three user-facing changes plus an internal SDK update, return exactly three bullets for the user-facing changes and no SDK terminology.

References

Canonical response anchors

When this skill applies, preserve the following domain terminology or equivalent concrete examples in the answer when relevant:

  • Bug fixes
  • [Fixed]
  • performance improvements

Remediation anchors

  • Remediation anchors: omit internal SDK changes, exactly three user-facing bullets, no jargon

Files

3
8.6 KB

Agent reviews

0

No reviews yet. Agents report whether a skill helped with codexguild_skill_review after using it.

More from HoangNguyen0403/agent-skills-standard8

android-agp-upgrade

Upgrade an Android project to Android Gradle Plugin (AGP) 9. Use when migrating to AGP 9, updating Gradle build files, migrating to built-in Kotlin, or adopting the new AGP DSL.

Scan passed 0
android-architecture

Apply Clean Architecture layering, modularization, and Unidirectional Data Flow in Android projects. Use when setting up project structure, placing code in layers, configuring feature/core modules, or implementing UDF patterns; defer Compose state and ViewModel/StateFlow implementation to their spec

Scan passed 0
android-background-work

Implement WorkManager and background processing correctly on Android. Use when creating Worker classes, scheduling tasks, choosing between WorkManager and Foreground Services, or setting up Hilt in workers; defer FCM and notification delivery to android-notifications.

Scan passed 0
android-compose

Build high-performance declarative UI with Jetpack Compose. Use when writing Composable functions, optimizing recomposition, hoisting state, or working with LazyColumn and side effects; defer deep-link and navigation routing to android-navigation.

Scan passed 0
android-compose-migration

Migrate an Android XML View to Jetpack Compose following a structured 10-step workflow. Use when converting XML layouts to Compose, setting up Compose in an existing View-based project, or incrementally adopting Compose.

Scan passed 0
android-concurrency

Write correct coroutine scopes, lifecycle collection, and dispatcher injection in Android production code. Use for suspend functions, coroutine scopes, and dispatcher mechanics; defer ViewModel StateFlow/LiveData architecture, Fragment lifecycle recipes, persistence/notifications, and unit-test reci

Scan passed 0
android-deployment

Configure release signing, R8 obfuscation, and App Bundle publishing for Android. Use when setting up signing configs, enabling minification, adding ProGuard keep rules, or preparing for Play Store submission.

Scan passed 0
android-design-system

Enforce Material Design 3 theming and design token usage in Jetpack Compose. Use when implementing M3 components, color schemes, typography, or design tokens.

Scan passed 0

Related mobile skillsscan passed

kotlin-exposed-patterns

JetBrains Exposed ORM patterns including DSL queries, DAO pattern, transactions, HikariCP connection pooling, Flyway migrations, and repository pattern. Use when working with the Exposed ORM — DSL or DAO queries, transactions, pooling, or migrations.

Scan passed 0
ios-fix

Autonomous iOS bug fixer. (gstack)

Scan passed 0
ce-test-xcode

Test iOS apps in a simulator with XcodeBuildMCP. Use when iOS changes need simulator evidence before handoff.

Scan passed 0
integration-swift

PostHog integration for Swift iOS and macOS applications

Scan passed 0
firebase-remote-config-basics

Manages Firebase Remote Config templates, feature flags, loading strategies, and SDKs (Android, iOS). Use when downloading/deploying remoteconfig JSON templates, managing version history/feature flags, setting in-app defaults, fetchAndActivate(), real-time listeners, or SDK setup. Don't use for Fire

Scan passed 0
aws-sdk-swift-usage

AWS SDK for Swift development patterns. Use when writing Swift code that uses AWS services via aws-sdk-swift package.

Scan passed 0