chore(ship): prompt for PR evidence in the ship skill - #79
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
The
/shipcommand's Push-and-PR phase now prompts for evidence in the PR body — a Before / After with proof a reviewer can check:curl/API output, server stats/metrics, or a TUI screenshot. The Body line also asks to center the description on functional change and impact rather than a code walkthrough.Why
The ship flow already gathers validation, but the command didn't tell the agent to attach that proof to the PR. Reviewers benefit from seeing the change work, not reading that it does.
Before / After
Docs/skill-guidance only — no runtime behavior changes.
curl/API output, server stats/metrics, or a TUI screenshot), noting when there's no observable change.Risk
Checklist
Generated by Claude Code