Commits changes with concise, clear commit messages (under 52 characters). Automatically creates feature branches when committing from main/master branches, using simple names like 'johnmog-area-change'. Use when you want to commit changes with a meaningful message or need to safely work off main.
Creates commits strictly following Conventional Commits format. ALWAYS read BEFORE committing changes, amending commits, or when the user mentions git commits, conventional commits, or commit messages.
Manage git worktrees for parallel branch development using custom git scripts (git-newtree, git-killtree, git-maingulp). Use when creating new worktrees, listing active worktrees, or closing/merging worktrees back to main. All worktrees are stored in .tree/ subdirectories of the repository.
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Stages specific lines from git diffs when hunk-level staging is too coarse. Use when a file contains multiple unrelated changes that need separate semantic commits, split commits, partial staging, or cherry-picking specific lines. Requires git-lines tool on PATH.
Manages git operations: worktree creation, branch management, commits, PRs, semantic versioning, daily rebase workflow, and PR feedback handling. Use when: Creating branches/worktrees, committing, pushing, versioning, handling PR feedback Triggers: create worktree, commit, push, rebase, version, PR, PR feedback
Start work on a Feature/Bug/Chore issue by creating a git worktree. Use when user wants to work on something, implement a feature, start development, or confirms work on a Linear issue. Uses Linear's auto-generated branch name and gwq for worktree creation. Do NOT load for: Thinking issues, code review, deployment.
Use the /fix-feature slash command to diagnose and fix bugs with a review loop. Use when: addressing defects or regressions.
Second step in building instruction context for codebase
Guide for writing conventional commits with gitmoji
Rewrite git history using git-filter-repo (not filter-branch)
This skill should be used when the user wants to clean up a feature branch's history using git-hex (squash/fixup commits, reorder/drop/split commits, or rebase a branch onto main) without using an interactive terminal. Trigger phrases include: "clean up my branch", "polish history", "squash these commits", "fixup commits", "rebase onto main", "rewrite commits".
Systematically triage incoming GitHub issues for the docent project
分析 Git 历史，发现"逻辑耦合"（总一起改的文件）和"热点"（高频修改的复杂模块）。基于 Adam Tornhill 的《Your Code as a Crime Scene》方法论。
TDD 워크플로우, Git Worktree, Phase 번호, 태스크 독립성 규칙이 적용된 TASKS.md를 생성합니다. /socrates 완료 후 자동 호출되거나 독립적으로 실행 가능합니다.
コミットをsquashして1つに集約し、Draft PRを作成するワークフロー。複数のコミットを1つに整理してからPRを作成します。
Analyze git changes to determine release scope (marketplace/plugin/variants)
Proactively remind about Gabe-OS workflows when context may have been lost, especially after /compact operations. Prevent manual implementation by checking for existing specs first.
Conventional Commits仕様に従ったコミットメッセージを作成する。コミット時に必ず使用すること。
To be used merging current branch into main branch to keep it up to date. Follow this instruction set for merging branches into main or master.
