메뉴
Auto-update the project changelog from git history. Analyzes commits, categorizes changes, and writes human-readable monthly changelog files.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | update-changelog |
| description | Auto-update the project changelog from git history. Analyzes commits, categorizes changes, and writes human-readable monthly changelog files. |
| argument-hint | [month: YYYY-MM or 'current'] |
Generate or update monthly changelog files in changelog/ from git commit history.
current: update the current month's changelogYYYY-MM (e.g. 2026-03): update a specific monthall: regenerate all months with commits$CWD/changelog/YYYY-MM.md (one file per month)changelog/2026-03.md# Get the argument
MONTH_ARG="$1" # e.g. "2026-03", "current", "all", or empty
# If empty or "current", use current month
# If "all", get all months with commits:
git log --format="%ad" --date=format:"%Y-%m" | sort -u
For each target month (YYYY-MM):
# Get commits with stats
git log --since="YYYY-MM-01" --until="YYYY-MM+1-01" \
--pretty=format:"%h|%ad|%s" --date=short --stat
Group changes by date, then categorize each commit:
| Category | When to use |
|---|---|
| Added | New files, features, skills, agents, scripts |
| Changed | Modified existing files, updates, refactors |
| Removed | Deleted files, removed features |
| Renamed | Moved or renamed files/skills |
| Fixed | Bug fixes |
Tips for good changelog entries:
Write/update the file at changelog/YYYY-MM.md:
# Changelog - Month Year
## YYYY-MM-DD
### Added
- **thing-name** - Brief description
### Changed
- **thing-name** - What changed and why
### Removed
- **thing-name** - Why removed or what replaced it
Rules:
## section per day that has commits### categories that have entriesShow the user what was written/updated. Do NOT commit - let the user review.
Expert guidance for creating, building, and using Claude Code agents and the Task tool. Use when working with agents, setting up agent configurations, understanding how agents work, or using the Task tool to launch specialized agents.
Complete SaaS ideation to implementation workflow - from idea discovery to task breakdown
Run structured APEX implementation (Analyze, Plan, Execute, eXamine) with parallel agents, tests, adversarial review, and proof-backed verification. Use for features, bug fixes, or code changes that need disciplined execution and real-flow evidence.
Deep iterative research using progressive flow psychology (diverge-analyze-converge-execute) with parallel agents, skeptical analysis, and multi-perspective synthesis. Use for thorough topic exploration, decision-making research, or when you need battle-tested conclusions.
Automated CI/CD pipeline fixer - watches CI, fixes errors locally, commits, and loops until green. Use when CI is failing and you want to automatically fix and verify changes.
Improve unclear UX copy, error messages, microcopy, labels, and instructions. Makes interfaces easier to understand and use.