git-commitExecute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff
git-push-branchPush the current branch to the remote under a speaking branch name derived from the last conventional commit (<type>/<scope>-<description>). Use when the user asks to push their branch, publish their work, push before opening a PR, or push with a meaningful branch name. Hard guard: NEVER pushes the
git-rebase-branchRebase the current branch onto the latest default branch (detected dynamically from the remote — main, develop, or whatever origin/HEAD points to), safely. Use when the user asks to rebase, update their branch with the default branch, sync with the default branch, resolve a "branch is behind" state,
github-authenticationGenerates, validates, and persists a GitHub personal access token (PAT) to the user-global ~/.claude/settings.json, so it is created once and valid in every repository. Use this skill whenever a GitHub token is needed, missing, expired, or must be refreshed — before any task that calls the GitHub AP
github-cancelAbandon the work in progress: close its pull request (or turn it into a draft), drop the local branch, and return to a clean base. The symmetric inverse of github-publish — the way to undo an attempt at sending work. Always confirms first, spelling out exactly what will be lost and that closing a pu
github-my-prsShow where the user stands: what they are working on right now, the pull requests they have open, the review comments waiting for them, and what they can do next — resume a piece of work, or abandon it. This is the way back to work that was left behind: switching to a pull request from the list rest
github-newMove on to something else: leave the work in progress behind and return to a clean, up-to-date base branch, ready to start fresh. Nothing is discarded silently — if the current work only exists locally (uncommitted changes or commits never pushed), the user is asked what to do with it first, because
github-open-prOpen a GitHub pull request for the current branch via the GitHub MCP server (mcp__github__create_pull_request). Use when the user asks to open a PR, create a pull request, or submit their branch for review. Derives owner/repo from the git remote, uses the current branch as head and the default branc
github-publishEnd-to-end "send my work to GitHub": commit the current changes as a Conventional Commit, then either open a pull request for new work or add to the pull request already open for it, and finally ask whether to keep going or move on. Recognises whether the current work is already published, so a seco
github-updateGet the latest version: bring whatever the user is currently on up to date, choosing the right method for their situation — a clean base is pulled, work that was never sent is rebased onto the latest base, and work with an open pull request is updated through GitHub itself so nothing already sent is