Development

Command

/pr

Create a GitHub PR from current branch with unpushed commits — discovers templates, analyzes changes, pushes

affaan-m@affaan-m

GitHub

From plugin

ecc

239k109 skills72 agents109 commands7 hooks

Install

> /plugin marketplace add affaan-m/ECC
> /plugin install ecc@ecc

How it fires

How this command gets triggered: by you, by Claude, or both.

Fires itselfClaude auto-loads it when your prompt matches the work.
You can call itInvoke it directly when you want it.
Slash command/pr

Context preview

What this command does when you run it.

Create a GitHub PR from current branch with unpushed commits — discovers templates, analyzes changes, pushes

Command definition

pr.md

description: "Create a GitHub PR from current branch with unpushed commits — discovers templates, analyzes changes, pushes"
argument-hint: "[base-branch] (default: main)"

Create Pull Request

**Input**: `$ARGUMENTS` — optional, may contain a base branch name and/or flags (e.g., `--draft`).

**Parse `$ARGUMENTS`**:

Extract any recognized flags (`--draft`)
Treat remaining non-flag text as the base branch name
Default base branch to `main` if none specified

---

Phase 1 — VALIDATE

Check preconditions:

git branch --show-current
git status --short
git log origin/<base>..HEAD --oneline

| Check | Condition | Action if Failed | |---|---|---| | Not on base branch | Current branch ≠ base | Stop: "Switch to a feature branch first." | | Clean working directory | No uncommitted changes | Warn: "You have uncommitted changes. Commit or stash first." | | Has commits ahead | `git log origin/<base>..HEAD` not empty | Stop: "No commits ahead of `<base>`. Nothing to PR." | | No existing PR | `gh pr list --head <branch> --json number` is empty | Stop: "PR already exists: #<number>. Use `gh pr view <number> --web` to open it." |

If all checks pass, proceed.

---

Phase 2 — DISCOVER

PR Template

Search for PR template in order:

1. `.github/PULL_REQUEST_TEMPLATE/` directory — if exists, list files and let user choose (or use `default.md`) 2. `.github/PULL_REQUEST_TEMPLATE.md` 3. `.github/pull_request_template.md` 4. `docs/pull_request_template.md`

If found, read it and use its structure for the PR body.

Commit Analysis

git log origin/<base>..HEAD --format="%h %s" --reverse

Analyze commits to determine:

**PR title**: Use conventional commit format with type prefix — `feat: ...`, `fix: ...`, etc.
If multiple types, use the dominant one
If single commit, use its message as-is
**Change summary**: Group commits by type/area

File Analysis

git diff origin/<base>..HEAD --stat
git diff origin/<base>..HEAD --name-only

Categorize changed files: source, tests, docs, config, migrations.

Planning Artifacts

Check for related artifacts produced by `/plan-prd`, `/plan`, or the legacy PRP workflow:

`.claude/prds/` — PRDs this PR implements a milestone of
`.claude/plans/` — Plans executed by this PR
`.claude/PRPs/prds/` — legacy PRP PRDs
`.claude/PRPs/plans/` — legacy PRP implementation plans
`.claude/PRPs/reports/` — legacy PRP implementation reports

Reference these in the PR body if they exist.

---

Phase 3 — PUSH

git push -u origin HEAD

If push fails due to divergence:

git fetch origin
git rebase origin/<base>
git push -u origin HEAD

If rebase conflicts occur, stop and inform the user.

---

Phase 4 — CREATE

With Template

If a PR template was found in Phase 2, fill in each section using the commit and file analysis. Preserve all template sections — leave sections as "N/A" if not applicable rather than removing them.

Without Template

Use this default format:

## Summary

<1-2 sentence description of what this PR does and why>

## Changes

<bulleted list of changes grouped by area>

## Files Changed

<table or list of changed files with change type: Added/Modified/Deleted>

## Testing

<description of how changes were tested, or "Needs testing">

## Related Issues

<linked issues with Closes/Fixes/Relates to #N, or "None">

Create the PR

gh pr create \
  --title "<PR title>" \
  --base <base-branch> \
  --body "<PR body>"
  # Add --draft if the --draft flag was parsed from $ARGUMENTS

---

Phase 5 — VERIFY

gh pr view --json number,url,title,state,baseRefName,headRefName,additions,deletions,changedFiles
gh pr checks --json name,status,conclusion 2>/dev/null || true

---

Phase 6 — OUTPUT

Report to user:

PR #<number>: <title>
URL: <url>
Branch: <head> → <base>
Changes: +<additions> -<deletions> across <changedFiles> files

CI Checks: <status summary or "pending" or "none configured">

Artifacts referenced:
  - <any PRDs/plans linked in PR body>

Next steps:
  - gh pr view <number> --web   → open in browser
  - /code-review <number>       → review the PR
  - gh pr merge <number>        → merge when ready

---

Edge Cases

**No `gh` CLI**: Stop with: "GitHub CLI (`gh`) is required. Install: <https://cli.github.com/>"
**Not authenticated**: Stop with: "Run `gh auth login` first."
**Force push needed**: If remote has diverged and rebase was done, use `git push --force-with-lease` (never `--force`).
**Multiple PR templates**: If `.github/PULL_REQUEST_TEMPLATE/` has multiple files, list them and ask user to choose.
**Large PR (>20 files)**: Warn about PR size. Suggest splitting if changes are logically separable.

Read it on GitHub ↗

Ships withecc

Your agent can write code, but ECC gives it a coordinated engineering system and toolbox: it plans before it builds, verifies changes with tests, reviews its own work from a fresh context, remembers what matters, and turns repeated wins into reusable skills

Get the whole plugin

Stats

Python TypeScript JavaScript React Bash

+7 tags

Kotlin PHP Git GitHub Anthropic MCP Flutter

239,015

Stars

36,306

Forks

Active

Maintenance

JavaScript