agent-shepherd:resubmit-pr

To resubmit a git PR after direct codebase changes, generate a resubmit-context.json file describing the changes and rationale, then execute the agent-shepherd resubmit command to initiate a fresh review cycle.

A resubmit context is a JSON file detailing what changed and why, required to inform reviewers when re-entering the review cycle. It ensures updated context is passed into the new PR review after out-of-band edits.

Yes, resubmitting a PR marks the previous review cycle as superseded while retaining historical diffs. This preserves an auditable history of all changes and review contexts across the workflow.

Trigger a PR resubmit when changes are added directly to the codebase or outside the standard review cycle. It creates a fresh review context while linking back to the prior cycle, unlike starting a completely new review.

No, the resubmit workflow requires a resubmit-context.json file to describe the changes and rationale. This context informs reviewers and maintains auditability when re-entering the review cycle.

The resubmit workflow is limited to PRs with changes made outside the normal review flow. It requires manually generating a JSON context file and specifically targets the Agent Shepherd review cycle, not generic git workflows.