본문으로 건너뛰기
cccskills
무료GitHub에 공개

app-store-changelog

Turn git history since a release tag or specified reference into clear App Store release notes. Identify user-visible changes, remove duplicates and internal maintenance work, and draft concise bullets that explain what changed for users.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

Create user-facing App Store release notes by collecting and summarizing all user-impacting changes since the last git tag (or a specified ref). Use when asked to generate a comprehensive release changelog, App Store "What's New" text, or release notes based on git history or tags.

설치 방법 보기

이럴 때 유용합니다

  • Draft App Store What’s New text
  • Summarize changes since the last release tag
  • Create release notes for a specified commit range
  • Remove duplicates and internal work from release notes

포함된 파일(4)

  • SKILL.md2.9 KB
  • agents/openai.yaml220 B
  • references/release-notes-guidelines.md1.6 KB
  • scripts/collect_release_changes.sh796 B

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

App Store Changelog

Overview

Generate a comprehensive, user-facing changelog from git history since the last tag, then translate commits into clear App Store release notes.

Workflow

1) Collect changes

  • Run scripts/collect_release_changes.sh from the repo root to gather commits and touched files.
  • If needed, pass a specific tag or ref: scripts/collect_release_changes.sh v1.2.3 HEAD.
  • If no tags exist, the script falls back to full history.

2) Triage for user impact

  • Scan commits and files to identify user-visible changes.
  • Group changes by theme (New, Improved, Fixed) and deduplicate overlaps.
  • Drop internal-only work (build scripts, refactors, dependency bumps, CI).

3) Draft App Store notes

  • Write short, benefit-focused bullets for each user-facing change.
  • Use clear verbs and plain language; avoid internal jargon.
  • Prefer 5 to 10 bullets unless the user requests a different length.

4) Validate

  • Ensure every bullet maps back to a real change in the range.
  • Check for duplicates and overly technical wording.
  • Ask for clarification if any change is ambiguous or possibly internal-only.

Commit-to-Bullet Examples

The following shows how raw commits are translated into App Store bullets:

Raw commit messageApp Store bullet
fix(auth): resolve token refresh race condition on iOS 17• Fixed a login issue that could leave some users unexpectedly signed out.
feat(search): add voice input to search bar• Search your library hands-free with the new voice input option.
perf(timeline): lazy-load images to reduce scroll jank• Scrolling through your timeline is now smoother and faster.

Internal-only commits that are dropped (no user impact):

  • chore: upgrade fastlane to 2.219
  • refactor(network): extract URLSession wrapper into module
  • ci: add nightly build job

Example Output

What's New in Version 3.4

• Search your library hands-free with the new voice input option.
• Scrolling through your timeline is now smoother and faster.
• Fixed a login issue that could leave some users unexpectedly signed out.
• Added dark-mode support to the settings screen.
• Improved load times when opening large photo albums.

Output Format

  • Title (optional): "What's New" or product name + version.
  • Bullet list only; one sentence per bullet.
  • Stick to storefront limits if the user provides one.

Resources

  • scripts/collect_release_changes.sh: Collect commits and touched files since last tag.
  • references/release-notes-guidelines.md: Language, filtering, and QA rules for App Store notes.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Investigate bugs, crashes, and intermittent failures without changing code. Multiple agents examine evidence from different angles, then produce ranked possible causes, confidence levels, and the smallest steps needed to confirm the diagnosis.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Investigating the cause of a crash
  • Tracing a bug introduced by recent changes
  • Examining failures that occur intermittently
Dimillian/Skills4천2026년 3월 30일 업데이트

github

무료

Use the gh command-line tool to manage GitHub issues and pull requests, check CI automated checks, and inspect workflow failures. Retrieve failed-step logs or query the GitHub API for specific information in structured output.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Creating pull requests
  • Listing repository issues
  • Investigating failed CI checks and logs
Dimillian/Skills4천2026년 3월 30일 업데이트

Build and run an iOS project on an already running simulator using XcodeBuildMCP. Inspect screens, tap controls, enter text, and capture screenshots and logs to investigate how the app behaves while running.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Building and running an app in an iOS simulator
  • Checking screens through taps, typing, and swipes
  • Capturing screenshots to inspect the display
Dimillian/Skills4천2026년 3월 30일 업데이트

Build, refactor, or review macOS menubar apps using Tuist and SwiftUI. Separate data models, networking, state management, and views, then align project definitions and launch scripts for consistent local builds and restarts.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Creating a macOS menubar utility
  • Separating networking and state management from views
  • Organizing Tuist project definitions
Dimillian/Skills4천2026년 3월 30일 업데이트

Create and package macOS apps with SwiftPM, Swift’s package manager, without an Xcode project. Templates and scripts cover project setup, building, app bundles, launching, and optional signing, Apple notarization, and update feed generation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Starting a macOS app with SwiftPM
  • Packaging an executable and resources into an .app bundle
  • Preparing a signed and notarized release
Dimillian/Skills4천2026년 3월 30일 업데이트

Coordinate large code refactors or rewrites across multiple agents. It organizes parallel analysis, assigns clear file ownership, schedules work around dependencies, and checks individual changes and their integration against agreed requirements.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Refactoring code across many files
  • Dividing implementation work among multiple agents
  • Planning changes across dependent modules
Dimillian/Skills4천2026년 3월 30일 업데이트

Dimillian의 스킬 모두 보기

이 스킬의 문제 신고