Find your next open-source project

Search by name, purpose, or keyword — or paste a GitHub repository URL
All skills

pr

Write a PR body with a visual summary, before/after evidence, and merge risk notes.

When to use it

You've finished a change and opened a PR, but the description is still blank or a wall of prose.

For example

You say

Use the pr skill to write the body for my PR that adds a RunSkillButton to the session toolbar and streams results into a new SkillResultCard.

You get
  • Component tree diff
  • Before/after test output
  • Merge danger assessment

How it works

  • Summary picks the smallest visual — pseudocode, call tree, file tree, Mermaid, or diff — that makes the point clear.
  • Evidence pairs a before and after, favoring screenshots for visual changes and test output for logic changes.
  • Merge Danger labels the change a one-way or two-way door and names its blast radius.