Base directory for this skill: /Users/soph/Work/entire/devenv/cli_experiments_2/.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

ARGUMENTS: 0.8.42

Added the 0.8.42 entry to CHANGELOG.md. Summary of what I did:

Data gathered: 9 PRs merged since v0.8.1 (via git log v0.8.1..HEAD --merges), cross-checked against the PRs already documented in the 0.8.1 entry so nothing was double-counted. Trailing direct-to-main follow-up commits (judge-timeout sweep, mirror-list sort refinements, git-remote hint tweaks) were folded into their parent feature bullets.

Contributors: all internal (evisdren, Victor/gtrrz-victor, Stefan/Soph, Peyton/peyton-alt, paul/toothbrush, dependabot) per the team-members memory → no Thanks section.

The entry:

Added — cross-region code search (WIP, behind ENTIRE_CODE_SEARCH=1; #1616 + #1674 combined); entire repo mirror list --name/--sort (#1665 + #1679 combined, reflecting the final --name naming)
Changed — entire review no default reviewer timeout + judge 5m→20m (#1664); org/project/repo/grant promoted out of labs (#1672); git-remote-entire missing-cluster-host hint (#1649)
Fixed — mirror get clone URLs via the cluster login server (#1676)
Housekeeping — aws-actions/configure-aws-credentials bump (#1670)

One judgment call worth flagging: I placed #1649 (git-remote-entire hint) under Changed rather than Fixed — it improves messaging on a failure path rather than repairing broken behavior. Easy to move to Fixed if you'd prefer.

Note also the version jump — the previous stable tag is v0.8.1 and you asked for 0.8.42 (not 0.8.2). I used 0.8.42 as given; let me know if that was a typo for 0.8.2.