hoangnguyen0403/common-store-changelog
skills/common/common-store-changelog/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add hoangnguyen0403/agent-skills-standard common-store-changelogInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jul 15, 2026, 3:27 AM131.6s3 files scanned
SKILL.md
- name:
- common-store-changelog
- description:
- 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.
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
- Collect: Run
git log <last-tag>..HEAD --oneline(or use provided commit list). If no tag exists, use full history. - Triage: Scan commits and touched files. Group by theme:
New,Improved,Fixed. Drop internal-only. - 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. - Draft — Google Play: Compress App Store draft to ≤ 500 chars. Prioritise top 3–5 user-facing changes.
- 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
- Commit-to-Bullet Examples — load when mapping specific commits to bullets
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
Related Skills
hoangnguyen0403/common-operator-profile
testing
VerifiedTrustedCommunity
Infer the requesting operator's technical fluency from message content (never ask directly) and adapt register — business, hybrid, or technical — across SDLC workflow output. Use when starting sdlc, brainstorm-feature, plan-feature, verify-work, publish-notes, or session-report, or whenever a request's phrasing signals a non-technical or cross-stack operator.
524SKILL.mdUpdated Jul 12, 2026
hoangnguyen0403/database-transactions
documentation
VerifiedTrustedCommunity
Define transaction boundaries, locking, and consistency guarantees for multi-step writes. Use when designing atomic operations, retries, idempotency, or concurrent write behavior.
524SKILL.mdUpdated Jun 19, 2026
hoangnguyen0403/database-schema-design
development
VerifiedTrustedCommunity
Design relational or document schemas from access patterns, cardinality, and lifecycle. Use when modeling entities, choosing embed vs normalize, or shaping schema boundaries before implementation.
524SKILL.mdUpdated Jun 19, 2026
hoangnguyen0403/database-query-performance
data-ai
VerifiedTrustedCommunity
Diagnose database latency with explain plans, index ownership, and query-shape review. Use when a query is slow, an index is missing, or scans and N+1 patterns appear.
524SKILL.mdUpdated Jun 19, 2026