---

name: create-pr description: Creates GitHub pull request with links to architecture docs, feedback files, and comprehensive test plan. Run after implementation is complete. context: fork agent: general-purpose allowed-tools: Task, Read, Bash, Glob user-invocable: true

Create Pull Request

This skill creates a comprehensive GitHub pull request with links to architecture documentation, review feedback, and a test plan.

When to Use This

Run this skill after completing implementation and addressing review feedback:

• Feature implementation complete
• Review feedback addressed (optional but recommended)
• Commits pushed to feature branch
• Ready to submit for code review

Workflow Steps

Step 1: Detect Context

Automatically detect:

1. Current branch name: git branch --show-current
2. Feature name from branch (e.g., feature/payment-processing → payment-processing)
3. Commits since main: git log main..HEAD --oneline

If feature name can't be detected, ask the user.

Step 2: Verify Prerequisites

Check that:

• Current branch is not main or master
• There are commits to push
• Architecture docs exist (specs.md, frontend.md, backend.md)
• On a feature branch

If on main/master:

CopyError: You are currently on the main branch.

Please create a feature branch first:
git checkout -b feature/<feature-name>

Then run /create-pr again.

If no commits:

CopyError: No commits found since main branch.

Please make your changes and commit them before creating a PR.

Step 3: Invoke GitHub Expert Agent

Use the Task tool to invoke the github-expert agent in "PR mode":

CopyTask tool with:
- subagent_type: general-purpose
- description: "Create pull request for <feature-name>"
- prompt: "You are now acting as the github-expert agent in PR MODE.

Read the agent instructions at .claude/agents/github-expert.md and follow them precisely.

The feature is '<feature-name>' on branch '<branch-name>'.

Your task:
1. Read architecture documents:
   - docs/features/<feature-name>/specs.md
   - docs/features/<feature-name>/frontend.md
   - docs/features/<feature-name>/backend.md

2. Check for feedback files (if they exist):
   - docs/features/<feature-name>/frontend-feedback.md
   - docs/features/<feature-name>/backend-feedback.md

3. Get commit history:
   - Run: git log main..HEAD --oneline

4. Create a pull request using 'gh pr create' with:
   - Title: 'Feature: <Feature Name>'
   - Body including:
     - Summary (what was implemented)
     - Implementation details (backend & frontend highlights)
     - Architecture documentation links
     - Review feedback summary (if files exist)
     - Test plan (manual testing checklist)
     - Checklist (architecture compliance)
     - Generated with Claude Code signature

5. Use heredoc for proper formatting

6. Report the PR number and URL

Begin by gathering all necessary information."

Wait for the agent to complete.

Step 4: Report Success

After the agent completes:

CopyPull request created successfully!

PR: #<number>
URL: <GitHub URL>

The PR includes:
✓ Summary of implementation
✓ Backend and frontend highlights
✓ Links to architecture documentation
✓ Review feedback summary (if available)
✓ Comprehensive test plan
✓ Architecture compliance checklist

Next steps:
1. Review the PR on GitHub
2. Request reviewers
3. Address any review comments
4. Merge when approved

Error Handling

gh CLI Not Available

If gh command not found:

CopyError: GitHub CLI (gh) is not installed or not authenticated.

Please install and authenticate:
1. Install: brew install gh
2. Authenticate: gh auth login

Then run /create-pr again.

Missing Architecture Documents

If architecture docs are missing:

CopyWarning: Some architecture documents not found for '<feature-name>'.

Missing:
- docs/features/<feature-name>/specs.md
- docs/features/<feature-name>/frontend.md

The PR will be created, but it's recommended to have architecture docs.

Continue anyway? (y/n)

Not on Feature Branch

If on main/master:

CopyError: Cannot create PR from main/master branch.

Current branch: main

Please create a feature branch:
git checkout -b feature/<feature-name>

Then make your changes and run /create-pr again.

No Commits

If no commits since main:

CopyError: No new commits to include in the PR.

Current branch: <branch-name>
Commits since main: 0

Please make changes and commit them before creating a PR.

PR Format

The github-expert agent will create a PR with this structure:

Copy## Summary
[Brief description of what was implemented]

## Implementation Details

### Backend
- Implemented hexagonal architecture with Domain/Application/Infrastructure layers
- Created Feature aggregate with value objects
- Implemented use cases: CreateFeatureUseCase, GetFeatureUseCase
- [Key architectural decisions]

### Frontend
- Implemented Inertia.js pages: Index, Show, Create
- Used shadcn/ui components: Button, Form, Input, Card
- Created single-action controllers
- [Key UI decisions]

## Architecture Documents
- [Specs](docs/features/<feature-name>/specs.md)
- [Frontend Architecture](docs/features/<feature-name>/frontend.md)
- [Backend Architecture](docs/features/<feature-name>/backend.md)

## Review Feedback
[If feedback files exist]
Addressed issues from code review:
- [Link to frontend-feedback.md]
- [Link to backend-feedback.md]

## Test Plan
- [ ] Manual testing: User can create a new feature
- [ ] Manual testing: User can view feature list
- [ ] Run unit tests: `php artisan test`
- [ ] Run frontend tests: `npm test`
- [ ] Verify all acceptance criteria from specs.md met

## Checklist
- [ ] Code follows hexagonal architecture rules (@docs/ai-rules/backend.md)
- [ ] Code follows frontend patterns (@docs/ai-rules/frontend.md)
- [ ] Code follows clean code principles (@docs/ai-rules/clean-code.md)
- [ ] All tests passing
- [ ] No console errors in browser
- [ ] Database migrations tested

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Important Guidelines

Branch Detection

Try to be smart about detecting the feature name:

1. Extract from branch name: feature/payment-processing → payment-processing
2. Check for recent feature directories in docs/features/
3. Ask user if ambiguous

Feedback File Handling

Feedback files are optional:

• Check if they exist
• Include summary in PR if they do
• Don't fail if they don't exist

Test Plan

Extract test cases from:

• specs.md acceptance criteria
• frontend.md user flows
• backend.md use cases

Success Criteria

The workflow succeeds when:

• Branch and feature name detected
• Prerequisites verified
• github-expert agent invoked
• PR created with comprehensive description
• PR URL returned to user
• User guided on next steps

Tone & Style

• Be clear and helpful
• Provide specific error messages with solutions
• Show what was created (PR number, URL)
• Guide user to next steps
• Use checkmarks for visual feedback

Your role is to ensure the user has a well-structured pull request that clearly communicates what was implemented, references all architecture documentation, and provides a clear test plan for reviewers.