> common-store-changelog
Generate user-facing release notes for the Apple App Store and Google Play Store by collecting git history, triaging user-impacting changes, and drafting store-compliant changelogs. Enforces character limits (App Store ≤4000, Google Play ≤500), tone, and bullet format. Use when generating release notes, app store changelog, play store release, what's new, or version release notes for any mobile app. (triggers: generate changelog, app store notes, play store release, what's new, release notes, ve
curl "https://skillshub.wtf/HoangNguyen0403/agent-skills-standard/common-store-changelog?format=md"Store Changelog Standard
Priority: P1
Generate concise, user-benefit-focused release notes compliant with both App Store and Google Play limits.
Always-Apply Rules
- Character limits: App Store ≤ 4000 chars. Google Play ≤ 500 chars — validate before output.
- Benefit language: Write what the user gains, not what code changed. "Faster checkout" not "refactored cart service".
- Bullet-only format: One sentence per bullet. No paragraphs. No headers inside the notes.
- Drop internal commits: Exclude
chore,refactor,ci,build,test, dependency bumps, and config changes — no user impact. - Deduplicate: Merge commits touching the 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. 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 a 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 a 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.
References
- Commit-to-Bullet Examples — load when mapping specific commits to bullets
> related_skills --same-repo
> golang-tooling
Go developer toolchain — gopls LSP diagnostics, linting, formatting, and vet. Use when setting up Go tooling, running linters, or integrating gopls with Claude Code. (triggers: gopls, golangci-lint, golangci.yml, go vet, goimports, staticcheck, go tooling, go lint)
> common-ui-design
Design distinctive, production-grade frontend UI with bold aesthetic choices. Use when building web components, pages, interfaces, dashboards, or applications in any framework (React, Next.js, Angular, Vue, HTML/CSS). (triggers: build a page, create a component, design a dashboard, landing page, UI for, build a layout, make it look good, improve the design, build UI, create interface, design screen)
> common-owasp
OWASP Top 10 audit checklist for Web Applications (2021) and APIs (2023). Load during any security review, PR review, or codebase audit touching web, mobile backend, or API code. (triggers: security review, OWASP, broken access control, IDOR, BOLA, injection, broken auth, API review, authorization, access control)
> common-llm-security
OWASP LLM Top 10 (2025) audit checklist for AI applications, agent tools, RAG pipelines, and prompt construction. Load during any security review touching LLM client code, prompt templates, agent tools, or vector stores. (triggers: LLM security, prompt injection, agent security, RAG security, AI security, openai, anthropic, langchain, LLM review)