From workbranch
Show the current ticket, worktree, PR status, and recent commits for the active branch
How this skill is triggered — by the user, by Claude, or both
Slash command
/workbranch:work-statusThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
When this skill is invoked, follow these steps:
When this skill is invoked, follow these steps:
git branch --show-current
If on main or master, tell the user there's no active work branch. Suggest /work to start something.
Read .workbranch.json for team prefix (default: ENGG).
Parse the branch name to extract the ticket ID by matching the pattern TEAM-\d+ anywhere in the branch name.
Example: fix/ENGG-456-invoice-timeout → ENGG-456
If no ticket ID is found in the branch name, note that this branch isn't linked to a Linear ticket.
If a ticket ID was found:
linear issue view TICKET_ID --json --no-pager
Display:
Detect if inside a linked worktree:
git rev-parse --git-dir
git rev-parse --git-common-dir
If they differ, show the current worktree path via pwd. Otherwise note this is the main worktree.
git status --short
Show if the worktree is clean or has uncommitted changes.
git log --oneline -5
Show the last 5 commits on this branch.
gh pr view --json state,url,title,statusCheckRollup,reviews,number 2>/dev/null
If a PR exists, display:
If no PR exists, note that no PR has been opened yet. Suggest /work-pr when ready.
Format all sections in a clean, readable summary. Example:
## Active Work
**Ticket:** ENGG-456 — Invoice upload timeout on files over 20MB
**Status:** In Progress | **Assignee:** Philip Dodds
**URL:** https://linear.app/team/issue/ENGG-456
**Branch:** fix/ENGG-456-invoice-timeout
**Worktree:** ~/kodexa-wt/fix-ENGG-456-invoice-timeout (clean)
**Recent commits:**
abc1234 fix(extraction): increase upload timeout
def5678 test: add upload timeout test
**PR:** not opened yet — run /work-pr when ready
npx claudepluginhub pdodds/workbranch --plugin workbranchGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.