no-deferred-work
Use during all development - no TODOs, no FIXMEs, no "we'll add this later"; do it now or get explicit deferral permission
create-git-commit
根據 Git Repository 的風格建立 Commit。當使用者要求，或 Agent 需要建立 Commit 時，必須使用此技能。
workflow-orchestrator
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.
git-commit-stage
Manages staging/commits. Use for add/commit/amend. Triggers - save changes, contributions.
agent-manifest-aligner
AGENTS.md와 CLAUDE.md 파일 간 연결 및 충돌 해결. 프로젝트에 AGENTS.md가 존재할 때 CLAUDE.md가 이를 참조하도록 심볼릭 링크를 설정한다. 두 파일의 내용이 상충하면 사용자에게 확인하여 해결한다. "AGENTS.md 연결", "CLAUDE.md 설정", "매니페스트 정렬", "agents 연동" 같은 요청이나 프로젝트 초기화 시 트리거된다.
git-workflow
Git運用・ブランチ戦略・コミット規約・PR管理の包括的なガイド。ブランチ戦略の選択、コミットメッセージ規約、コンフリクト解決、Git hooks活用など、Gitに関する全ての判断基準と手順を提供します。
commit-message-style
Apply commit message style: conventional commits format (type: subject), imperative mood, <50 char subject, explain why in body. Use when writing commits, reviewing commit messages, or discussing git history.
commit-message-generator
Generate clear, concise commit messages from git diffs. Use when writing commit messages, reviewing staged changes, or formatting git history.
create-branch
Create a new git branch from main/master with a maximum of 17 characters. Prompts for branch name or infers from context.
squashing-commits
Reorganizes commits and working changes into optimal structure. Use when: user wants to squash commits, reorganize history, or clean up commits.
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
github-content
Fetch GitHub issues, PRs, repo contents, and code using the gh CLI. Use when the user shares GitHub URLs (issues, PRs, repos, source files) or asks about GitHub content. The gh CLI provides complete content that web fetching often misses due to JavaScript rendering.
forking-worktree
Use when user wants to create new autonomy branch with dedicated worktree for parallel agent workflows
gf3-pr-verify
Verify GF(3) skill conservation on pull requests. Ensures every contribution
git-workflow
Activates when user needs help with git operations including branching, rebasing, merging, cherry-picking, stashing, and resolving conflicts. Triggers on "help me rebase", "fix merge conflict", "create branch", "git history", "undo commit", "squash commits", or any git workflow questions.
conventional-commits
Commit message standards following Conventional Commits specification. Use this when writing commit messages for the Hey Jarvis project.
