Base directory for this skill: /Users/soph/Work/entire/devenv/cli_experiments/.claude/skills/changelog

Changelog Generation

Generate a changelog entry for a new release by analyzing merged PRs since the last tag.

Parameters

The user provides:

Version number -- e.g., 0.5.3
Additional PRs -- optionally, PRs not yet merged that should be included

Step 1: Gather Data

Find the previous release tag: git tag --sort=-version:refname | head -1
List all merge commits since that tag: git log <tag>..HEAD --merges --format='%s' | grep -v "Merge branch"
Get PR details with: gh pr list --state merged --base main --search "merged:><tag-date>" --json number,title,author --limit 50
List contributors: git log <tag>..HEAD --format='%an' --no-merges | sort | uniq -c | sort -rn

Step 2: Identify External Contributors

To determine if a contributor is external, check for an @entire.io email:

If they have an @entire.io email anywhere in git history, they are internal. Only list external contributors in the Thanks section.

Also check the memory file at memory/project_team_members.md for known internal/external mappings.

Step 3: Write the Entry

Insert the new version section at the top of CHANGELOG.md, after the header and before the previous version.

Format

Follow the existing style in CHANGELOG.md exactly:

Style Rules

Sections: Added, Changed, Fixed, Housekeeping, Thanks. Omit empty sections.
Each bullet: starts with a dash, concise description, PR link(s) at the end
Group related PRs into a single bullet when they're part of the same feature/fix
Work-in-progress features: call out explicitly, e.g., "Feature X (work in progress): ..."
Known limitations: note inline, e.g., "Note: subagent tracking is not yet supported due to..."
Thanks section: only external contributors. Name what they contributed specifically.
Dependency bumps: group into a single Housekeeping bullet unless a bump fixes a notable bug
PR links: always use full URL format [#N](https://github.com/entireio/cli/pull/N)
No trailing period on bullet items
Date: use the current date in YYYY-MM-DD format

Categorization Guide

Added: new features, new commands, new agent integrations, new CI workflows
Changed: behavior changes, API changes, UX changes, migrations
Fixed: bug fixes, E2E fixes, agent-specific fixes
Housekeeping: dependency bumps, docs, refactors, CI improvements, test improvements

3mo ago·40m

Added the 0.7.4 entry (dated 2026-06-04) at the top of CHANGELOG.md, covering the 21 PRs merged since v0.7.3.

Summary of the entry:

Added (6 bullets): silent login-token refresh and ENTIRE_TOKEN override + --version/--help for git-remote-entire, auth use tab-completion, generic slash-command skill events, and the grouped checkpoints v1.1 WIP work (#1316, #1329–#1332, #1335)
Changed (6 bullets): the auth UX simplification / PAT removal (#1341), HTTP User-Agent stamping (#1348), the two repo mirror create improvements (#1357, #1344), labs alignment (#1345), and cosmetic tweaks (#1343)
Housekeeping (3 bullets): auth review follow-ups (#1360), hermetic test (#1361), and grouped dependabot bumps

No Thanks section — every contributor since v0.7.3 is internal (paul/toothbrush, pfleidi, computermode, Stefan, Paulo, Andrea Nodari, Pat Leamon/stiak, dipree), confirmed against project_team_members.md and git email history.

I followed the version-line default (0.7.4, matching the existing nightly tags) per your selection. The v1.1 PRs are framed as "work in progress" to stay consistent with how 0.7.0 introduced them — let me know if you'd rather break any group out into separate bullets.

Added the 0.7.5 entry (dated 2026-06-04) at the top of CHANGELOG.md, covering the two PRs merged since v0.7.4:

Fixed (2 bullets):
- The checkpoint/session path-traversal → arbitrary-file-write vulnerability (#1365) — listed first given its security severity
- git-remote-entire now surfacing real per-ref push rejection reasons (#1364)

No Thanks section — both authors (Soph/Stefan, pjbgf/Paulo) are internal.

Note: the path-traversal fix is a security fix; the skill's section list (Added/Changed/Fixed/Housekeeping/Thanks) has no dedicated Security section, so I placed it under Fixed and led with it. If you'd prefer a ### Security section (Keep a Changelog supports it), say the word and I'll split it out.