Claude updates CHANGELOG/WIP without checking git log or issues first

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.