adamayoung/pr

Create a pull request

I'll create a pull request for the current branch by following these steps. If any steps fail, stop.

1. Run /format to format code
2. Check for formatting changes and commit them if needed with message "🤖 apply code formatting"
3. Run /lint to verify code style and quality
4. Run /build-for-testing to ensure project builds successfully with no warnings
5. Run /test to verify all tests pass
6. Spawn the code-reviewer agent to perform a code review of all changes. Pass it:
   • The full diff: git diff origin/main...HEAD
   • The list of changed files: git diff --name-only origin/main...HEAD
   • Instruct it to read full files (not just diff hunks) and compare with sibling implementations for pattern consistency
7. Summarize the code review findings:
   • List any critical or high-severity issues that should be addressed
   • List any medium-severity suggestions for improvement
   • Note any low-severity or stylistic recommendations
8. If there are critical/high-severity issues:
   • Recommend specific changes needed
   • Ask user for confirmation before proceeding (fix issues or continue anyway)
   • If user wants to fix issues, stop and let them address the feedback
9. Check if branch is up-to-date with main (warn if behind)
10. Run git status and git diff origin/main...HEAD to understand all changes
11. Analyze the commits and changes to generate an appropriate title and summary
12. Push the current branch to remote using git push (not gh CLI, which bypasses webhooks/workflows)
13. Create a PR using gh pr create with:
    • IMPORTANT: Title MUST start with a gitmoji prefix (e.g., "✨ Add new feature", "🐛 Fix bug", "📚 Improve documentation")
      • Refer to https://gitmoji.dev to use the correct emoji
      • Common: ✨ feature, 🐛 bugfix, ♻️ refactor, 🧪 tests, 📚 docs, 🔧 config, 🎨 style
    • A comprehensive summary with bullet points
    • Proper formatting with sections (Summary, Changes, Benefits, etc.)

The PR will include the Claude Code attribution footer.

$ARGUMENTS