Skip to content

chore(ship): prompt for PR evidence in the ship skill - #175

Merged
chaliy merged 1 commit into
mainfrom
claude/pr-description-standards-0xh7do
Aug 6, 2026
Merged

chore(ship): prompt for PR evidence in the ship skill#175
chaliy merged 1 commit into
mainfrom
claude/pr-description-standards-0xh7do

Conversation

@chaliy

@chaliy chaliy commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

What changed

The /ship command's Push-and-PR phase now prompts for evidence in the PR body — a Before / After with proof: CLI/API output or logs (fetch results, MCP responses). The Body line is also updated to reference .github/pull_request_template.md with the current sections (What changed / Why / Before / After / Risk / Checklist) and to center the description on functional change and impact.

Why

The ship flow already gathers validation, but the command didn't tell the agent to attach that proof to the PR, and its body reference still listed the old What/Why/How sections. Reviewers benefit from seeing the change work, not reading that it does.

Before / After

Docs/skill-guidance only — no runtime behavior changes.

  • Before: Body step said "use What / Why / How / Risk / Checklist."
  • After: references the PR template (What changed / Why / Before / After / Risk / Checklist) + functional framing, and adds an Evidence line (CLI/API output or logs), noting when there's no observable change.

Risk

  • Low
  • Skill/docs only; no source, config, or CI logic touched.

Checklist

  • Unit tests are passed — N/A (skill/docs only)
  • Smoke tests are passed — N/A
  • Documentation is updated
  • Specs are up to date and not in conflict

Generated by Claude Code

@chaliy
chaliy merged commit 710b88c into main Aug 6, 2026
11 checks passed
@chaliy
chaliy deleted the claude/pr-description-standards-0xh7do branch August 6, 2026 05:29
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.

2 participants