Loading...
Loading...
Found 30 Skills
Manage version control with Jujutsu (jj) — no staging area, immediate changes, smart rebasing. Use when navigating history, squashing, or pushing to Git remotes.
Automated git workflow helpers for common development tasks like creating feature branches, cleaning up merged branches, and interactive rebasing. Use when the user mentions git branching, branch cleanup, feature workflow, or git automation. No prerequisites required - uses native git commands.
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
Prepare a GitHub PR for merge by rebasing onto main, fixing review findings, running gates, committing fixes, and pushing to the PR head branch. Use after /review-pr. Never merge or push to main.
Git version control with branching, merging, and rebasing. Use for source control.
DubStack CLI reference. Use for managing stacked changes (git branches). Covers creating stacks, navigating, submitting PRs, rebasing (restacking), and undoing mistakes.
Master of Ceremonies for Git. Architect of High-Integrity Repositories. Expert in Git 3.0, Forensic Bisecting, and Interactive Rebasing.
Use this skill for ANY task involving jj or jujutsu version control. ALWAYS trigger when the user mentions jj, jujutsu, revsets, change IDs, bookmarks, or oplog. Also trigger when the user wants to squash, split, or reorder commits in a stack, write a revset query, absorb fixup changes, undo or restore a previous operation, resolve conflicts after rebasing, recover from force-pushes, rewrite protected/immutable commits, view change evolution (evolog), or try parallel approaches. Trigger even if "jj" is not explicitly said — "changes" instead of "commits", "stack" instead of "branch", "absorb", "squash into the right commit", "undo my last operation", "conflict after rebase", or "compare approaches in parallel" are strong jj signals. This skill contains critical non-obvious rules (like always using -m flags) that prevent broken workflows.
A comprehensive Git command assistant and workflow guide. Trigger whenever the user asks how to perform a specific Git operation, wants to know what a Git command does, needs help fixing a Git mistake, or wants guidance on Git best practices (like branching, rebasing, or squashing).
Manages version control with Jujutsu (jj), including rebasing, conflict resolution, and Git interop. Use when tracking changes, navigating history, squashing/splitting commits, or pushing to Git remotes.
Advanced git rebase patterns for linear history, stacked PRs, and clean commit management. Use when rebasing branches, cleaning up commit history, managing PR stacks, or converting merge-heavy branches to linear history. Covers --reapply-cherry-picks, --update-refs, --onto, and interactive rebase workflows.
Interactive git and GitHub tutor that teaches through hands-on practice in VS Code's terminal. Adapts to any skill level — from someone who's never opened a terminal to principal engineers filling knowledge gaps. Covers git commands, concepts, branching, merging, rebasing, GitHub workflows, and more. Tracks progress, streaks, and achievements in a `.git-tutor/` folder. USE THIS SKILL whenever the user wants to learn git, practice git, understand git concepts, get a git tutorial, learn GitHub, or says things like "teach me git", "I want to practice git", "help me understand branching", "git tutorial", "I'm new to git", "how does git work", "let's do more git practice", or asks to start the git tutorial. Also triggers for questions about git concepts when the user seems to be in a learning context rather than needing a quick answer for active development work.