reflexio: Skill for Claude Code

PR Creator

Create well-structured, reviewer-friendly pull requests following best practices.

CRITICAL: This skill MUST always result in a PR being created. Do NOT stop early, do NOT ask the user to run another command first. Handle all prerequisites (committing, branching, pushing) inline and proceed to gh pr create.

---

Workflow

Step 1: Pre-flight Checks

Run these checks before anything else:

1. Verify GitHub CLI authentication — run gh api user --jq '.login' to confirm the CLI is authenticated. If this fails, tell the user to run gh auth login first and stop.
2. Determine the base branch — default to main. If the user specifies a different base, use that. Capture as $BASE_BRANCH.

Step 2: Commit Uncommitted Changes

Run git status to check for uncommitted changes. If there are uncommitted changes, commit them directly — do NOT delegate to another skill or tell the user to commit first.

1. Stage changes — run git add <files> for relevant modified/untracked files. Do not stage .env or gitignored files.
2. Lint and format — if Python files are staged, run:

   ruff check --fix <files> && ruff format <files>
   

   Re-stage any modified files.
3. Commit — write a conventional commit message based on the staged diff:

   git commit -m "<type>: <description>"
   

   If precommit hooks modify files, re-stage with git add -u and retry (up to 3 times).

Step 3: Ensure Feature Branch

1. Check current branch — run git branch --show-current.
2. If on $BASE_BRANCH, create a feature branch:
   • Analyze the commits/changes to pick a descriptive name (e.g., feat/add-auth, fix/login-bug)
   • Run git checkout -b <branch-name>
3. If on a different branch, check whether the branch has PR-worthy commits vs $BASE_BRANCH:
   • Run git log $BASE_BRANCH..HEAD --oneline
   • If there are commits, use the current branch as-is
   • If there are NO commits (branch is at same point as base), this means something went wrong — investigate and fix