From qe-framework
Git branch workflow manager that creates branches, commits via Qcommit, and opens PRs. Use when starting feature, fix, hotfix, or any branch-based work.
How this skill is triggered — by the user, by Claude, or both
Slash command
/qe-framework:QbranchThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Manages the full branch lifecycle: create branch, commit changes (via Qcommit), push, and open PR. Prevents direct push to main.
Manages the full branch lifecycle: create branch, commit changes (via Qcommit), push, and open PR. Prevents direct push to main.
MANDATORY: All user confirmations MUST use the
AskUserQuestiontool. Do NOT output options as plain text — always call the tool.
User: "I'll develop a login feature"
→ Qbranch: creates feat/add-login, switches to it
User: "Push this as a PR"
→ Qbranch: pushes current branch, creates PR via gh
User: "Need an emergency fix"
→ Qbranch: creates hotfix/ branch from main
User: "Clean up branches"
→ Qbranch: deletes merged branches (local + remote)
| Type | Prefix | Purpose | Example |
|---|---|---|---|
| Feature | feat/ | New functionality | feat/add-login |
| Bug fix | fix/ | General bug fix | fix/order-calc |
| Hotfix | hotfix/ | Production emergency patch | hotfix/auth-crash |
| Chore | chore/ | Config, deps, cleanup | chore/cleanup-deps |
| Refactor | refactor/ | Code improvement, no behavior change | refactor/extract-utils |
| Docs | docs/ | Documentation only | docs/update-readme |
Direct push to main is blocked. If the current branch is main or master:
AskUserQuestion/Qbranch or /Qbranch start)Step 1: Select branch type
Use AskUserQuestion with 4 options:
Step 2: Get branch description
Use AskUserQuestion to ask for a short description (2-4 words, kebab-case).
Auto-convert spaces to hyphens, remove special characters.
Step 3: Create and switch
git checkout -b {type}/{description}
Report: Created and switched to {type}/{description}
/Qbranch commit)Delegates to Qcommit (Ecommit-executor). Identical to /Qcommit but adds a safety check:
/Qbranch pr)Step 1: Push current branch
git push -u origin {current-branch}
Step 2: Generate PR content Analyze commits on this branch (vs main) to auto-generate:
Step 3: Create PR
gh pr create --title "{title}" --body "{body}" --base main
Step 4: Report Show PR URL and summary.
/Qbranch cleanup)Step 1: Find merged branches
git branch --merged main | grep -v 'main\|master\|\*'
Step 2: Confirm deletion
Use AskUserQuestion to show the list and confirm:
Step 3: Delete
git branch -d {branch} # local
git push origin --delete {branch} # remote
/Qbranch status)Show current branch info:
gh pr list --head {branch})When no explicit mode is given, infer from context:
Qbranch orchestrates the workflow. Qcommit handles the commit execution.
Never duplicate Qcommit's responsibilities. Always delegate commit operations.
npx claudepluginhub inho-team/qe-framework --plugin qe-frameworkCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.