jackin-project/jackin-dev

jackin-release-notes

Use only when the user explicitly requests this skill. Classifies every PR merged since the last tag into Keep a Changelog categories and writes the [Unreleased] section of CHANGELOG.md.

First seen Jul 4, 2026

Installation

$ npx skills add jackin-project/jackin-dev --skill jackin-release-notes

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from jackin-project/jackin-dev · top by installs.

npx skills add jackin-project/jackin-dev

Browse all from jackin-project/jackin-dev

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 3
License LICENSES
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

LicenseApache-2.0

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,198 B
  • docs SUMMARY.md 211 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 381 installs

SKILL.md

jackin-release-notes

Classify every PR merged since the last release tag into a Keep a Changelog bucket, then write the [Unreleased] section of CHANGELOG.md. The bar is exhaustive — every merged PR accounted for, none dropped, none doubled.

When to use

  • Before a release, to populate the changelog.
  • When the operator asks to preview what the next release would contain.

When NOT to use

  • Cutting the release itself → jackin-release (it runs this skill as its notes step).

Process

  1. Find the boundary. LASTTAG=$(git describe --tags --abbrev=0); if none, start from the initial commit (git rev-list --max-parents=0 HEAD). TAGDATE=$(git log -1 --format=%aI "$LAST_TAG").

Done when you hold the boundary commit and its date.

  1. Gather merged PRs. gh pr list --state merged --base main --search "merged:>$TAG_DATE" --json number,title,labels,mergedAt.

Done when every PR merged after the tag is in the list.

  1. Classify each. Sort by Conventional Commits prefix and label:
Prefix / label Bucket
feat: / feature Added
fix: / bug Fixed
security: Security
refactor:, chore:, docs:, ci:, build: Changed
deprecate: Deprecated
remove: Removed
no match Changed (default)

Strip the prefix from the title; capitalize the first word (feat: add TUI launcherAdd TUI launcher).

Done when every PR sits in exactly one bucket.

  1. Catch ungrouped commits. git log <last-tag>..HEAD --oneline --no-merges; for each, gh pr list --state merged --search "<sha>". Commits with no PR land under Ungrouped commits.

Done when every non-merge commit since the tag is matched to a PR or listed.

  1. Write [Unreleased]. Keep a Changelog format: one section per non-empty bucket, each entry linking its PR ([#N](…/pull/N)). Replace the existing [Unreleased] block (between ## [Unreleased] and the next ## [) — ask before overwriting entries an operator already edited. Keep the <!-- next-header --> marker intact.

Done when CHANGELOG.md carries every merged PR under the right bucket, empty buckets omitted, and the marker survives.

  1. Present for review. Show the section; let the operator re-classify or reword. Do not proceed to a release until approved.

Idempotency

Safe to re-run: reads CHANGELOG.md fresh each time, asks before overwriting existing entries, fetches PR data live from GitHub.

Common mistakes

  • Dropping a PR that has no conventional-commit prefix — it defaults to Changed, never omitted.
  • Listing an empty bucket ("no Removed entries" is noise — drop the section).
  • Forgetting the PR link in each entry.
  • Overwriting an operator-edited [Unreleased] without asking.