Prepare all work before creating a pull request, optionally for the issue provided as argument
Prepare all work before creating a pull request. If an issue number is provided in $ARGUMENTS, use it. If no issue is provided, continue without requiring one.
Follow these steps:
Check current git status and branch information
git status and git branch to understand the current stateCreate branch if needed
Review commit history and code differences
git log and git diff main...HEAD to understand all changes from the main branchAdd changeset record if necessary
.changeset/ directory following changeset conventionpatch (0.0.x) — Users barely notice
minor (0.x.0) — Users can clearly perceive "something new"
major (x.0.0) — Users need to pay attention / adapt. Almost never use. Must ask user for explicit approval before using.
Ensure all changes are committed
docs/; it is for local copy/paste onlydocs/pr-*.md file was accidentally staged, remove it from the index before committing while keeping the local filePush the branch to remote
git push -u origin <branch-name> if neededCreate Markdown for PR Description
.github/PULL_REQUEST_TEMPLATE.mdCloses #<issue-number>Follow these commit types:
feat: New featuresfix: Bug fixesdocs: Documentation changesstyle: Code style changesrefactor: Code refactoringtest: Adding or updating testschore: Maintenance tasksbuild: Build system changesci: CI/CD changesperf: Performance improvementsrevert: Reverting previous commitsi18n: Internationalization changesai: AI-related featuresFormat: type(scope): description
.github/PULL_REQUEST_TEMPLATE.mdCLAUDE.md