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ใซ้ขใใๅ จใฆใฎๅคๆญๅบๆบใจๆ้ ใๆไพใใพใใ