claude-code - 💡(How to fix) Fix Claude updates CHANGELOG/WIP without checking git log or issues first [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#58715Fetched 2026-05-14 03:41:20
View on GitHub
Comments
1
Participants
2
Timeline
7
Reactions
0
Author
Participants
Timeline (top)
labeled ×2mentioned ×2subscribed ×2commented ×1
RAW_BUFFERClick to expand / collapse

Behavior

When asked to "update CHANGELOG and WIP", Claude adds only the changes from the current session without first inspecting:

  • git log since the last tag/release
  • Open/closed GitHub issues
  • Recent merged PRs

The result is a CHANGELOG that silently skips multiple real entries (feature commits, fixes, CI changes) and a WIP that still lists already-completed issues as pending.

Expected behavior

Before writing to CHANGELOG or WIP, Claude should:

  1. Run git log <last-tag>..HEAD --oneline to enumerate all commits since last release
  2. Check open issues (gh issue list) and recently closed issues
  3. Cross-reference commits against existing CHANGELOG entries to find gaps
  4. Only then produce the updated content

Actual behavior

Claude appended only the work done in the current conversation turn, silently omitting ~10 commits and incorrectly leaving two already-implemented issues (#52, #60) in the priority queue.

Impact

The user had to explicitly point out the gap twice before the correct behavior was triggered.

Reproduction

Ask Claude: "CHANGELOG, WIP, TODO도 최신화해줘" immediately after completing a coding task in a repo with several commits since the last CHANGELOG update. Claude will update only what it just did.

Suggested fix

Add a reminder or tool-use step in the CHANGELOG/WIP update flow: always call git log and gh issue list before writing, not after being corrected.


Reported by Claude itself, on behalf of user @debop.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Before writing to CHANGELOG or WIP, Claude should:

  1. Run git log <last-tag>..HEAD --oneline to enumerate all commits since last release
  2. Check open issues (gh issue list) and recently closed issues
  3. Cross-reference commits against existing CHANGELOG entries to find gaps
  4. Only then produce the updated content

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING