Skip to content

docs(workflow): Treat in-session requests on an open PR as feedback to record - #58

Open
DetweilerRyan wants to merge 1 commit into
mainfrom
docs/feedback-guard
Open

DetweilerRyan wants to merge 1 commit into
mainfrom
docs/feedback-guard

Conversation

@DetweilerRyan

@DetweilerRyan DetweilerRyan commented Nov 22, 2026 •

Copy link
Copy Markdown
Owner

Makes sure a fresh session treats the owner's requests in the session as feedback on an open pull request, and records them there before acting.

Requested in a Claude Code session, 2026-11-22, after the miss on #57 (recorded there):

i do want the guard because i don't wan't this to happen again with a new fresh session

What to look at

  • The new boundary in AGENTS.md. It's the only file every session loads, and the engineering index allows a boundary there when you ask for it to be loaded in every session. It points to Revising work rather than restating the steps.
  • The definition of feedback, now in revising-work.md's opening and in the index's "Read when" row: any request in the session that changes an open pull request, draft or ready, including an approval, a choice between offered options, or asking for something to be added, moved or renamed.

Decisions made

For the owner to confirm

Nothing.

Changed test expectations

Nothing.

Verification

Links

Follows #57. Relates to #47, where revising-work.md came from.

🤖 Generated with Claude Code

…back

AGENTS.md gains a boundary, loaded by every session, against acting on
the owner's feedback on an open pull request before recording it there,
and says that any request in the session that changes an open pull
request is feedback, approvals and choices between offered options
included. The workflow index's trigger for revising work and the
procedure's opening say the same, and the sidecar records the case on
#57 that prompted it, the second after #47.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@vercel

vercel Bot commented Nov 22, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
split Ready Ready Preview Nov 22, 2026 3:57am UTC

This branch has not been deployed

No deployments
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