Make PR

Overview

Use this skill to draft and open a PR with consistent, high-signal writing. Keep headings sparse and focus on the problem/feature explanation, context links, and practical code examples.

Workflow

1. Gather context from branch diff and related work.

• Capture what changed, why it changed, and who it affects.
• Find related issues/PRs and include links when relevant.

1. Draft the PR body with minimal structure.

• Start with 1-2 short introductory paragraphs.
• In those intro paragraphs, include clear bullets describing:
  • the feature and/or issue addressed
  • key behavior/API changes
  • expected impact
• If the change is extensive, expand to up to 3-4 paragraphs and include background context with related links.

1. Add required usage examples for feature work.

• If the PR introduces a new feature, include a comprehensive usage snippet.
• If it replaces or improves an older approach, include before/after examples.

1. Exclude redundant sections.

• Do not include Validation, Testing, or other process sections that are already implicit in PR workflow.
• Do not add boilerplate sections that do not help review.

1. Create the PR.

• Save the body to a temporary file and run:

gh pr create --base main --head <branch> --title "<title>" --body-file <file>

Body Template

Use this as a base and fill with concrete repo-specific details:

<One or two short intro paragraphs explaining the change and why it matters.>

- <Feature/issue addressed>
- <What changed in behavior or API>
- <Why this is needed now>

<Optional additional context paragraph(s), up to 3-4 total for large changes, including links to related PRs/issues.>

```ts
// New feature usage example
```

// Before

// After