Skip to content

dedalus-labs/wingman / .agents/skills/pr

Create a pull request using the wingman PR template. Injects git state, commit history, and diff stats automatically.

FileKindSize
SKILL.mdskill md1.9 KB
---
name: pr
description: Create a pull request using the wingman PR template. Injects git state, commit history, and diff stats automatically.
allowed-tools: Bash(git *), Bash(gh *), Bash(awk *), Bash(sort *), Read
argument-hint: "[base-branch] [--branch <source-branch>]"
---

## Context (auto-detected from HEAD)

- Current branch: !`git branch --show-current`
- Remote status: !`git status -sb | head -1`

## PR Template

Read `.github/PULL_REQUEST_TEMPLATE.md` and fill every section. The template is mandatory.
Do not free-form the PR body.

## Rules

- PR title: `type(scope): description` (conventional commit format, under 70 chars)
- Target branch: first positional arg from `$ARGUMENTS` if provided, otherwise `main`
- Source branch: if `--branch <name>` is in `$ARGUMENTS`, use that branch for diff/log
  commands instead of HEAD. This is needed when the PR branch lives in a different worktree
  or the main repo checkout.
- Push with `-u` if needed
- Use `gh pr create` with `--body "$(cat <<'EOF' ... EOF)"` for correct formatting
- **Hard limit: 500 changed LOC** (excluding generated files and lock files).
  If the diff exceeds 500 lines, do not create the PR. Instead, propose a
  stacked-PR plan: split changes into logical, independently reviewable PRs
  where each PR is under 500 LOC. Each stacked PR targets the previous one's
  branch (not main) until the final one merges the stack into main.
- Warn at 200 changed lines — suggest splitting proactively

## Task

1. Determine the source branch: use `--branch` value if provided, otherwise current HEAD
2. Gather context by running:
   - `git log --oneline origin/main..<source-branch>` (commits for this PR)
   - `git diff --stat origin/main..<source-branch>` (diff stats)
   - `git diff --name-only origin/main..<source-branch>` (changed files)
3. Push the branch if needed
4. Read the PR template
5. Create the PR with every template section filled
6. Return the PR URL
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 implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall