github-pr-create

github-pr-create

Create a pull request using gh pr create with an auto-generated description.

Behavior

1. Check git/gh user consistency:

   • Run git config user.name to get the local git identity
   • Run gh auth status to identify the active GitHub user
   • If gh auth status shows X Failed to log in ... (keyring) for all accounts (even though the user has authenticated):
     • This is a known keyring issue in some environments — treat it as a keyring-unavailable environment
     • Do NOT stop; proceed to the Keyring-unavailable fallback section below
   • If they differ:
     • If acting autonomously: run gh auth switch --user "$(git config user.name)"
       • If switch succeeds: continue
       • If switch fails: defer this skill. After all other work is done, report to the user: the git/gh user mismatch and that the switch failed
     • If not acting autonomously: stop the skill and ask the user to resolve the mismatch before continuing

2. Check current branch status by running git status and git branch

3. Inspect the commits ahead of the base branch by running (whichever base exists):

   • git log main..HEAD --oneline
   • git log develop..HEAD --oneline
   • git log master..HEAD --oneline

4. If on main or master branch, create a new feature branch

5. If there are uncommitted staged changes, use the git-commit skill to commit them first

6. Push the branch to remote using the git-push skill

7. Create a PR using gh pr create with auto-generated title and description

Branch Naming Convention

When creating a new branch, use the following prefixes based on the changes:

• feature/ - New features or enhancements
• fix/ - Bug fixes
• hotfix/ - Urgent fixes for production
• refactor/ - Code refactoring
• chore/ - Maintenance tasks

Example: feature/add-notification-timing, fix/resolve-login-error

PR Description Format

The PR description should be written in English and follow this structure: