git-worktrees
Use Git worktrees to isolate tasks and keep diffs small and parallelizable
Use Git worktrees to isolate tasks and keep diffs small and parallelizable
Git branch cleanup utility. Lists and deletes branches that have been merged to main. Use when user wants to clean up old branches, delete merged branches, or tidy up their git repository.
Create a GitHub issue. Use when the user wants to create an issue, open an issue, or report a bug/feature request.
MUST use when working with spec files in `specs/` directories, or when commands reference this skill for conventions.
Create or switch to feature branches with proper naming conventions. Use when user wants to start working on a new feature, start a feature. Generates feature/branch-name patterns from descriptions, checks existence, and creates/switches accordingly.
Guides contributors through adding new skills to the claude-code-skills repository via Pull Request with proper validation and documentation
Creates a sub-issue linked to a parent GitHub issue. Use when: user wants to create a sub-issue, break down an issue, or add child task.
GitHub issue state machine and code integration patterns. Covers state transitions (needs-triage → accepted → in-progress → completed), branch naming (feat/123-desc), PR linking (Closes
Use when updating specifications, comparing branches, or ensuring documentation reflects current implementation.
Use when user wants to compare two autonomy branches to see different approaches, metrics, and outcomes
Rebases current branch onto target with conflict resolution. Use when: user wants to rebase, update branch base, or linearize history.
Use after implementing features - 7-criteria code review with MANDATORY artifact posting to GitHub issue; blocks PR creation until complete
Stashes changes, rebases onto main, and reapplies stash. Use when: user wants to update branch while preserving uncommitted work.
When asked to commit, write clear git commit messages (50/72, present tense, subsystem prefixes like go-lcpd:).
WHEN: User asks about Go best practices, idiomatic patterns, or how to properly implement something in Go. Also when reviewing Go code or asking "what's the right way to..." WHEN NOT: Questions unrelated to Go programming or general coding questions
Jujutsu (jj) version control system - a Git-compatible VCS with novel features. Use when working with jj repositories, managing stacked/dependent commits, needing automatic rebasing with first-class conflict handling, using revsets to select commits, or wanting enhanced Git workflows. Triggers on mentions of 'jj', 'jujutsu', change IDs, operation log, or jj-specific commands.
Use when starting feature work that needs isolation from current workspace. Creates isolated git worktrees with smart directory selection and safety verification.
Use when starting a new feature - running /alto-feature-setup, updating objective.md, or running alto-new-run. Interactive workflow for feature initialization.
Create or update GitHub Pull Requests with the gh CLI, including deciding whether to create a new PR or only push based on existing PR merge status. Use when the user asks to open/create/edit a PR, generate a PR body/template, or says 'PRを出して/PR作成/gh pr'. Defaults: base=develop, head=current branch (same-branch only; never create/switch branches).
Use when user wants to safely remove an autonomy worktree while preserving the branch