NVIDIA-NeMo/DataDesigner / .agents/skills/create-pr
create-pr
VerifiedCreate a GitHub PR with a well-formatted description matching the repository PR template (flat Changes by default; optional Added/Changed/Removed/Fixed grouping). The argument may contain special instructions for the pull-request summary.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.5 KB |
SKILL.md
View on GitHub---
name: create-pr
description: Create a GitHub PR with a well-formatted description matching the repository PR template (flat Changes by default; optional Added/Changed/Removed/Fixed grouping). The argument may contain special instructions for the pull-request summary.
disable-model-invocation: true
metadata:
internal: true
---
# Create Pull Request
Create a well-formatted GitHub pull request for the current branch. The PR description must conform to the repository's PR template (`.github/PULL_REQUEST_TEMPLATE.md`).
## Arguments
`$ARGUMENTS` can be used for special instructions, such as:
- Specifying a base branch: "use base branch: develop"
- Guiding the summary: "emphasize the performance improvements in the summary"
- Adding context: "this is part of the auth refactor epic"
- Any other guidance for PR creation
Default base branch: `main` (unless specified in arguments)
## Step 1: Gather Information
Run these commands in parallel to understand the changes:
1. **Current branch**: `git branch --show-current`
2. **Uncommitted changes**: `git status --porcelain`
3. **Commits on branch**: `git log origin/main..HEAD --oneline`
4. **File changes summary**: `git diff --stat origin/main..HEAD`
5. **Full diff**: `git diff origin/main..HEAD`
6. **Recent commit style**: `git log -5 --oneline` (to match PR title convention)
7. **Repo info**: `gh repo view --json nameWithOwner -q '.nameWithOwner'` (for constructing file URLs)
**Important checks:**
- If uncommitted changes exist, warn the user and ask if they want to commit first
- If no commits ahead of main, inform the user there's nothing to PR
- If branch isn't pushed, you'll push it in Step 4
## Step 2: Analyze and Categorize Changes
Use change types below to **decide** how to write the Changes section (flat vs grouped). You still describe testing under **Testing**, not under these buckets.
### By change type (internal checklist)
- β¨ **Added**: New files, features, capabilities
- π§ **Changed**: Modified existing functionality
- ποΈ **Removed**: Deleted files or features
- π **Fixed**: Bug fixes
- π **Docs**: Documentation updates
- π§ͺ **Tests**: Test additions/modifications
### When to use optional grouping in **Changes**
- **Flat bullet list** (default): Small PRs, single theme, or when categories would be sparse or redundant.
- **Grouped subheadings** (`### β¨ Added`, `### π§ Changed`, `### ποΈ Removed`, `### π Fixed`): Large PRs, release-note-style summaries, or clearly distinct fix + feature mixes. **Omit any empty section** β do not leave placeholder headings.
### Identify attention areas
Flag for special reviewer attention:
- Files with significant changes (>100 lines)
- Changes to base classes, interfaces, or public API
- New dependencies (`pyproject.toml`, `requirements.txt`)
- Configuration schema changes
- Security-related changes
## Step 3: Generate PR Title
Use conventional commit format matching the repo style:
- `feat:` for new features
- `fix:` for bug fixes
- `docs:` for documentation
- `refactor:` for refactoring
- `chore:` for maintenance
- `test:` for test changes
If commits have mixed types, use the primary/most significant type.
## Step 4: Create the PR
1. **Push branch** (if needed):
```bash
git push -u origin <branch-name>
```
2. **Build the PR body** using the repository's template structure.
**Default β flat Changes** (remove the HTML comment block from the template when filling in, or replace with your bullets only):
```markdown
## π Summary
[1-3 sentences: what this PR does and why. Focus on the "why".]
## π Related Issue
[Fixes #NNN or Closes #NNN β link to the issue this addresses]
## π Changes
- [Bullet list of key changes]
- [Link to key files when helpful for reviewers]
- [Reference commits for specific changes in multi-commit PRs]
## π§ͺ Testing
- [x] `make test` passes
- [x] Unit tests added/updated (or: N/A β no testable logic)
- [ ] E2E tests added/updated (if applicable)
## β
Checklist
- [x] Follows commit message conventions
- [x] Commits are signed off (DCO)
- [ ] Architecture docs updated (if applicable)
```
**Optional β grouped Changes** (only when Step 2 criteria apply; omit empty sections):
```markdown
## π Changes
### β¨ Added
- [...]
### π§ Changed
- [...]
### π Fixed
- [...]
```
(Include `### ποΈ Removed` only when something was deleted.)
If there are genuinely important attention areas for reviewers, add an **Attention Areas** section after Changes:
```markdown
## π Attention Areas
> β οΈ **Reviewers:** Please pay special attention to the following:
- [`path/to/critical/file.py`](https://github.com/<owner>/<repo>/blob/<branch>/path/to/critical/file.py) β [Why this needs attention]
```
3. **Execute**:
```bash
gh pr create --title "<title>" --body "$(cat <<'EOF'
<body>
EOF
)"
```
4. **Return the PR URL** to the user.
## Section Guidelines
- **Summary**: Always include β be concise and focus on the "why", not just the "what"
- **Related Issue**: Always include if an issue exists. Use `Fixes #NNN` for bugs, `Closes #NNN` for features/tasks
- **Changes**: Default to a flat list. Use Added/Changed/Removed/Fixed subheadings only for large or mixed PRs; never emit empty subsection headings
- **Testing**: Check off items that apply. Mark N/A items explicitly rather than leaving them unchecked without explanation
- **Checklist**: Check off items that are true. Leave unchecked with a note if something doesn't apply
- **Attention Areas**: Only include if there are genuinely important items; omit for simple PRs
- **Links**: Include links to code and commits where helpful for reviewers:
- **File links require full URLs** β relative paths don't work in PR descriptions
- Link to a file: `[filename](https://github.com/<owner>/<repo>/blob/<branch>/path/to/file.py)`
- Link to specific lines: `[description](https://github.com/<owner>/<repo>/blob/<branch>/path/to/file.py#L42-L50)`
- Use the branch name (from Step 1) in the URL so links point to the PR's version of files
- Reference commits: `abc1234` β GitHub auto-links short commit SHAs in PR descriptions
- For multi-commit PRs, reference individual commits when describing specific changes
## Edge Cases
- **No changes**: Inform user there's nothing to create a PR for
- **Uncommitted work**: Warn and ask before proceeding
- **Large PRs** (>20 files): Summarize by directory/module; grouped Changes often helps here
- **Single commit**: PR title can match commit message
- **No related issue**: Note "N/A" in the Related Issue section rather than omitting it
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |