dedalus-labs/wingman / .agents/skills/pr
pr
VerifiedCreate a pull request using the wingman PR template. Injects git state, commit history, and diff stats automatically.
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
$ARGUMENTSif provided, otherwisemain - 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
-uif needed - Use
gh pr createwith--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
- Determine the source branch: use
--branchvalue if provided, otherwise current HEAD - 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)
- Push the branch if needed
- Read the PR template
- Create the PR with every template section filled
- Return the PR URL
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: 319k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 319k | 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: 319k | 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: 319k | Updated | Claude CodeCodex | Verified | Install |