Skip to content
cccskills
FreePublished on GitHub

pr

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

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md1.9 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Design engineering principles for making TUI interfaces feel polished. Use when building Textual widgets, reviewing TUI code, implementing transitions, focus states, alignment, spacing, or any visual detail work. Triggers on TUI polish, design details, "make it feel better", "feels off", layout alignment, color consistency, responsive sizing.

The English summary is being prepared. Showing the original description.

dedalus-labs/wingman182Updated Apr 25, 2026

commit

Free

Create a git commit with conventional commit format. Injects current git state automatically.

The English summary is being prepared. Showing the original description.

dedalus-labs/wingman182Updated Apr 25, 2026

Explain system behavior, request flows, architecture, or implementation logic as short 4chan-style greentext lines. Use when the user asks for a step-by-step explanation, says "explain the logic", asks for "greentext", or wants terse sequential reasoning with each line starting with `>`.

The English summary is being prepared. Showing the original description.

dedalus-labs/wingman182Updated Apr 25, 2026

issue

Free

Create a GitHub issue using the wingman issue templates (bug, feature). Injects branch and commit context automatically.

The English summary is being prepared. Showing the original description.

dedalus-labs/wingman182Updated Apr 25, 2026

Review PR comments from GitHub. Fetches inline review comments and issue comments, classifies by blocking vs non-blocking, and summarizes actionable items.

The English summary is being prepared. Showing the original description.

dedalus-labs/wingman182Updated Apr 25, 2026

Create a changelog-style promotion PR between two branches. Use for release promotions or branch-to-branch merges with a structured changelog.

The English summary is being prepared. Showing the original description.

dedalus-labs/wingman182Updated Apr 25, 2026

See all skills by dedalus-labs

Report a problem with this skill