Changelog 0.7.6

Claude Code·Opus 4.8[1m]·Soph·3mo ago·12min·1 Checkpoint·1 file change·+38·15.9K tokens

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

  1. Find the previous release tag: git tag --sort=-version:refname | head -1
  2. List all merge commits since that tag: git log <tag>..HEAD --merges --format='%s' | grep -v "Merge branch"
  3. Get PR details with: gh pr list --state merged --base main --search "merged:><tag-date>" --json number,title,author --limit 50
  4. 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·6m

Added the 0.7.6 changelog entry (dated 2026-06-15) at the top of CHANGELOG.md. The version comes from the in-development nightly tags (v0.7.6-nightly.*).

Summary of what I captured across ~30 PRs since v0.7.5:

  • Added — entire blame/why, trail review CLI, browser-default login (--device/--server), enable backend reporting, and the work-in-progress checkpoints v1.1 push/mirror/doctor/topology work
  • Changed — multi-type search, auth-context-aware control-plane & data-API commands, prompt-based step counting, flowchart diagrams, checkpoint rewind deprecation, runner configs
  • Fixed — trail list/API alignment, browser sign-in hardening, Pi skill-capture lock, cygwin ANSI rendering
  • Housekeeping — test config/keychain isolation, flaky-test fix, spec refresh, lint fix, docs link, dependency bumps
  • Thanks — @suhaanthayyil (the only external contributor; everyone else has an @entire.io address)

A couple of judgment calls worth a glance:

  • I grouped paul's COR-389/393/395 auth work into a single "follow the active auth context" Changed bullet plus the login bullet in Added — tell me if you'd rather split them out.
  • I placed checkpoints v1.1 under Added as "work in progress" (matching how 0.7.4 framed it). Some of those PRs (#1376, #1351) are arguably Changed/refactor — say the word and I'll move them.

can you update that blame and why are in labs

3mo ago·21.1s

Done — both the Added bullet and the Thanks line now describe entire blame and entire why as labs commands.