Skip to content

Explain the PR snapshot, not the commit-by-commit journey#1

Open
perborgen wants to merge 1 commit into
mainfrom
explain-snapshot-not-commits
Open

Explain the PR snapshot, not the commit-by-commit journey#1
perborgen wants to merge 1 commit into
mainfrom
explain-snapshot-not-commits

Conversation

@perborgen

Copy link
Copy Markdown
Contributor

Explainers kept narrating the commits that led up to the PR — iterations, reverts, fixups — instead of the final state of the change.

The prompt tells the agent it has "the full repo, git history" and to "reconstruct intent from the PR title, body, commit messages, and linked issues", but never said that history is input-only. Combined with the "human story" / "journey" framing, agents reinterpreted the development history as the story to tell.

This adds one explicit bullet to the investigation brief: explain the PR's net change as it stands right now; commit messages and branch history are investigation input only, never narration.

🤖 Generated with Claude Code

Explainers kept narrating the branch's development history (iterations,
reverts, fixups) instead of the net change. The prompt hands the agent
git history and commit messages for intent reconstruction but never said
they are input-only, so they leaked into the narration.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant