메뉴
Add a new entry to CHANGELOG.md for a feature, fix, or release. Handles both [Unreleased] additions and splitting a release section.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Add a new device profile to podcast-tui's config.json so episodes sync to an MP3 player / DAP / USB drive with device-appropriate filenames and folder layout. Covers device research, field selection, and safe config editing.
Prepare a new release by finalizing CHANGELOG, tagging, and verifying builds. Covers everything before pushing the tag that triggers CI.
Query the GitHub project board to find the next stack-ranked issue to work on. Returns the top actionable Todo item from the Task List view, checking issue dependencies and filtering out epics, closed issues, and blocked items.
Reorder items on the Task List project board to reflect current priorities. Supports full strategic reranks and targeted insertions. Always shows proposed order for user confirmation before executing.
Write a checkpoint file at session end so the next session can pick up exactly where you left off. Captures what was done, what's next, key decisions, and reminders.
Bootstrap a new session from a previous session's checkpoint. Reads the handoff file, confirms the project board state, and prepares to continue work.
| name | update-changelog |
| description | Add a new entry to CHANGELOG.md for a feature, fix, or release. Handles both [Unreleased] additions and splitting a release section. |
Open CHANGELOG.md and find the ## [Unreleased] section at the top.
Select the appropriate subsection:
Add under the correct subsection in [Unreleased]. Follow this format:
## [Unreleased]
### Added
**Feature Name — Month Year**
- **Main thing**: One-line summary
- Sub-detail with more context
- Another sub-detail
- Commands or keybindings introduced: `:command`, `Shift+D`
- Config fields added: `downloads.new_field` (default: `true`)
- Tests added: N unit tests
When tagging a release, rename [Unreleased] to the new version:
## [1.7.0] - YYYY-MM-DD
### Added
<content from [Unreleased]>
Then add a fresh empty ## [Unreleased] above it.
Use this when multiple releases were cut without the changelog being maintained and you need to attribute features to the correct version.
⚠️ Never infer version attribution from feature names, "Phase N" labels, or narrative alone. Features named "Phase 2" and "Phase 3" may ship in different releases. Always verify with timestamps.
Step 1 — Get release timestamps
gh api repos/lqdev/podcast-tui/releases --jq '.[] | "\(.tag_name) published: \(.published_at)"'
Step 2 — Get the canonical PR list for each release
GitHub auto-generates a PR list in every release body. This is the ground truth:
gh release view vX.Y.Z --repo lqdev/podcast-tui --json body
The body contains every PR merged between the previous and current tag, with links.
Step 3 — Verify individual PR timing (if release body is ambiguous)
gh pr view N --repo lqdev/podcast-tui --json number,title,mergedAt
A PR belongs to the earliest release whose publishedAt timestamp is >= the PR's mergedAt.
Step 4 — Write entries per release For each release, group the PRs from its body by change type (Added / Changed / Fixed) and write entries following the format above.
v1.9.0 published: 2026-02-20T15:51:52Z
v1.8.0 published: 2026-02-19T17:15:41Z
PR #80 mergedAt: 2026-02-20T03:53:20Z → in v1.9.0 (after v1.8.0 cutoff)
PR #58 mergedAt: 2026-02-18T18:36:38Z → in v1.8.0 (after v1.7.0, before v1.8.0)