gh-issue-lifecycle
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
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
Use during all development - no TODOs, no FIXMEs, no "we'll add this later"; do it now or get explicit deferral permission
根據 Git Repository 的風格建立 Commit。當使用者要求,或 Agent 需要建立 Commit 時,必須使用此技能。
Orchestrates git workflow for Python feature/release/hotfix development. Loads and coordinates other skills based on current context. Includes PR feedback handling via work-item generation. Use when: - User says "next step?" or "continue workflow" - Working in git repo with TODO_[feature|release|hotfix]_*.md files - Need to determine workflow phase and load appropriate skills - Handling PR feedback via work-items Triggers: next step, continue, what's next, workflow status, PR feedback Coordinates: tech-stack-adapter, git-workflow-manager, bmad-planner, speckit-author, quality-enforcer, workflow-utilities Context management: Prompt user to run /context when context usage is high, then /init to reset before continuing workflow.
Manages staging/commits. Use for add/commit/amend. Triggers - save changes, contributions.
AGENTS.md와 CLAUDE.md 파일 간 연결 및 충돌 해결. 프로젝트에 AGENTS.md가 존재할 때 CLAUDE.md가 이를 참조하도록 심볼릭 링크를 설정한다. 두 파일의 내용이 상충하면 사용자에게 확인하여 해결한다. "AGENTS.md 연결", "CLAUDE.md 설정", "매니페스트 정렬", "agents 연동" 같은 요청이나 프로젝트 초기화 시 트리거된다.
Git運用・ブランチ戦略・コミット規約・PR管理の包括的なガイド。ブランチ戦略の選択、コミットメッセージ規約、コンフリクト解決、Git hooks活用など、Gitに関する全ての判断基準と手順を提供します。