Loading...
Loading...
Found 44 Skills
Use when merging a branch to main without touching the primary worktree directly, when /ship or /reflect needs to integrate work, or when autonomous mode blocks direct main commits
Push branch and create GitHub pull request. Use when the user wants to open a PR, submit changes for review, or push and create a pull request.
Guide for working in parallel with other agents. Use when another agent is already working in the same directory, or when you need to work on multiple features simultaneously. Covers git worktrees as the recommended approach.
Linear ticket lifecycle for any project. Use when starting work on a Linear issue, ending work on an issue, or asking what to work on next. Triggers: start KAT-N, pick up, implement, finish, complete, done with, close, what's next, next ticket, next issue. Handles blocker validation, status transitions, context loading, branch creation, evidence gating, and chain promotion.
Resume a paused experiment. Checkout the experiment branch, read results history, continue iterating.
Quick status check for current branch and PR state showing local changes, CI results, reviews, and merge readiness. Use when user wants branch status, PR state, CI check results, review status, or merge readiness. Use for "pr status", "what's the status", "is my PR ready", "check CI". Do NOT use for creating PRs, pushing changes, or fixing review comments.
Create a PR with dev as base using the pull request template. Use when opening a new PR.
Git worktree management with safe defaults and flexible placement strategies. Use when users ask to: (1) create a new worktree or work on multiple branches in parallel, (2) list existing worktrees, (3) remove or clean up worktrees, (4) manage worktree placement (subfolder vs sibling directory), or any other git worktree operations.
Generate or update tests for changed files in the current git branch, using statement coverage as the evaluation metric (target: 80%+). Use when: (1) the user asks to "write tests for my changes", "add tests for the current branch", or "improve coverage", (2) after implementing a feature to ensure adequate test coverage, (3) before a PR to verify changed code is tested. Supports Vitest and Cargo projects. Invoked with /test-generator or phrases like "generate tests", "test my changes", "cover the diff".
Fetches a Jira ticket and starts implementation with a branch and plan. Use when (1) starting work on a Jira ticket, (2) creating a feature branch from a Jira issue, (3) beginning implementation of a story or task, (4) picking up a ticket from the backlog, or (5) user provides a Jira ticket ID to work on.
Fetches Jira ticket context, creates a branch, and drafts an implementation plan
DubStack CLI reference. Use for managing stacked changes (git branches). Covers creating stacks, navigating, submitting PRs, rebasing (restacking), and undoing mistakes.