GitHub PR Creator

Prepares structured, review-ready GitHub Pull Requests. Ensures every PR includes problem context, verification commands, and issue references (Fixes #123).

1. Purpose

Turn raw branch commits into a professional Pull Request description that reviewers can approve quickly.

2. When to Use

Use this skill when:

• Opening a pull request after completing code and test changes.
• Preparing PR descriptions via gh pr create or web interface.
• Linking pull requests to issues (Closes #42).

3. When Not to Use

• Do not use to review another contributor's PR; use github-pr-reviewer.
• Do not use to write end-user release notes; use release-notes-drafter.

4. Required Inputs

• title: Short PR title following Conventional Commits (e.g. feat(auth): add token refresh).
• branch_name: Source branch name.
• base_branch: Target branch (default: main).

5. Missing-Input Behavior

1. If title is not specified: generate title from git log -n 1 --pretty=%s.
2. Inspect git diff <base_branch>...HEAD to verify changed files before writing summary.

6. Procedure

Follow these numbered actions:

1. Action 1: Verify Git Diff
   • Check git status and ensure all intended changes are committed.
2. Action 2: Draft PR Body
   • Summary of Changes.
   • Motivation / Linked Issue (Fixes #...).
   • Testing Evidence (command and output).
   • Breaking Changes (if any).
3. Action 3: Check Branch Health
   • Ensure branch builds and tests pass locally.
4. Action 4: Emit PR Content
   • Format per Section 8.

7. Decision Rules

• If PR introduces breaking API changes: prepend BREAKING CHANGE: in title and description.
• Always link issue number if known.

8. Output Format

Emit the PR description using this template:

## Description
[Brief 1-2 sentence summary of what this PR does.]

## Linked Issue
Fixes #[issue_number]

## Key Changes
- [Change 1]
- [Change 2]

## Testing & Verification
- Test command: `[e.g. npm test]` -> `[34 passed, 0 failed]`
- Manual check: `[curl or CLI test]`

## Checklist
- [x] Unit/integration tests added or updated
- [x] Linters and type-checkers pass with exit code 0
- [x] Documentation updated (if applicable)

9. Verification Checklist

• PR title follows Conventional Commits.
• Test evidence included.
• Issue linked with Fixes #....
• Zero uncommitted temporary files.

10. Common Failures and Recovery

11. Stop or Escalation Conditions

Stop and ask the user when:

• Target base branch is protected and requires specialized credentials.

12. Examples

Example 1: Successful Execution

Input:

Branch: feat/jwt-refresh
Base: main
Issue: #88
Changes: Added refresh token endpoint, updated tests

Output:

## Description
Implements the `/v1/auth/refresh` endpoint allowing clients to exchange valid refresh tokens for short-lived access tokens.

## Linked Issue
Fixes #88

## Key Changes
- Added `POST /v1/auth/refresh` route in `src/routes/auth.ts`.
- Added refresh token database lookup with revocation checks.
- Added regression test in `tests/auth_refresh.test.ts`.

## Testing & Verification
- Automated tests: `npm test tests/auth_refresh.test.ts` (4 passed, 0 failed).
- Type check: `npx tsc --noEmit` exited code 0.

## Checklist
- [x] Unit/integration tests added
- [x] Linters and type-checkers pass
- [x] Documentation updated

Example 2: Ambiguous or Missing Input

Input:

Make a PR.

Output:

### GitHub PR Creator: Halted - Missing Details

- **Status**: Halted

Please provide:
1. The branch name or target issue.
2. The core objective of the pull request.

Example 3: Expected Final Output

Output:

## Description
Fixes zero division crash when calculating cart discounts with 0 items.

## Linked Issue
Fixes #104

## Key Changes
- Added defensive check in `src/cart.py` for empty item list.

## Testing & Verification
- `pytest tests/test_cart.py` passed (8 passed in 0.05s).