Publish

You are assisting with pushing commits and managing pull requests. Follow these steps:

1. Initial State Assessment

• Run git status to check current branch and sync status
• Run git fetch origin to get latest remote updates
• Determine push strategy based on branch state

2. Push Strategy

If branch is ahead of remote (normal push):

git push -u origin HEAD

If branch has diverged from remote (after rebase):

git push --force-with-lease

3. PR Management

After pushing, check for existing PR:

gh pr view

If PR exists:

• Review the current PR description
• Compare with the actual changes (git diff origin/main...HEAD)
• Update description if it doesn’t accurately reflect the changes: gh pr edit

If no PR exists:

• Create a new PR following the conventions below
• Ask user whether to create as draft or ready for review

PR Description Conventions

Template Selection

1. Check for project template:

   find . -maxdepth 2 -iname "pull_request_template.md" -print -quit
   

2. Select template based on result:

   • Project template exists: Read and use the project template
   • No project template: Read references/pr-template.md and use it

IMPORTANT: Always read the selected template file before creating the PR description. Never create a PR description without first reading a template.

Title

• MUST match a commit message subject line exactly
• If multiple commits, ask user which to use

Language

• Match template language if project template exists
• Default: English
• Japanese: Use polite form (敬語)

Signature

Always end with:

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

4. Final Output

• Display the PR URL
• Show the current commit history relative to main