Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification | ็พๅจใฎใฏใผใฏในใใผในใใใฎๅ้ขใๅฟ ่ฆใชๆฉ่ฝ้็บใ้ๅงใใ้ใใพใใฏๅฎ่ฃ ่จ็ปใๅฎ่กใใๅใซไฝฟ็จ - ในใใผใใชใใฃใฌใฏใใช้ธๆใจๅฎๅ จๆงๆค่จผใไผดใๅ้ขใใใgit worktreeใไฝๆ
Format git commit messages correctly, avoiding HEREDOC syntax issues in favor of multiline strings
Git GTR (Git Worktree Runner) ใฎๅฉ็จๆนๆณใ็็ฅใใฆใใพใใ git worktree ใไฝฟใฃใใใฉใณใใฎ็ฎก็ใๆไฝใฏ git-gtr ใไฝฟใฃใฆใใ ใใใ
Use before any code changes - hard gate ensuring work never happens on main branch, with proper feature branch creation from correct base
Manage monorepo and multi-package Python projects with uv workspaces. Covers workspace configuration, member dependencies, shared lockfiles, and building. Use when user mentions uv workspaces, Python monorepo, multi-package projects, workspace members, or shared dependencies across packages.
Creates a fixup commit and performs autosquash rebase. Use when: user wants to fixup a commit, amend a previous commit, or squash into existing commit.
This skill should be used when the user asks about "rust workspace", "rust best practices", "cargo workspace setup", "rust code organization", "rust dependency management", "rust testing strategy", "rust project", "scalable rust", "rust CI setup", or needs guidance on senior-level Rust development patterns, workspace design, code organization strategies, or production-ready Rust architectures.
FVH (Forum Virium Helsinki) pre-commit hook standards and configuration. Use when configuring pre-commit hooks in FVH repositories, checking hook compliance, or when the user mentions FVH pre-commit, conventional commits, or hook configuration.
MUST use when working with spec files in `specs/` directories, or when commands reference this skill for conventions.
Automatically fold uncommitted changes into appropriate commits on a feature branch. Use when applying review feedback, fixing bugs in feature branches, or maintaining atomic commit history without manual interactive rebasing. Particularly useful for making corrections to recent commits without creating messy "fixes" commits.
Teaches when to use gabb_structure for efficient file exploration. Use gabb_structure before reading large files in supported languages.
Use to keep GitHub Project fields synchronized with actual work state - updates status, verification, criteria counts, and other project-specific fields
Comprehensive work session initialization orchestrator that validates environment, creates properly named branches, and prepares development environment for new tasks
Use when user wants to create new autonomy branch from current commit or specific past iteration
Use at the beginning of every work session - establishes context by checking GitHub project state, reading memory, verifying environment, and orienting before starting work
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
Review a mixed working tree and produce (and optionally execute) a small, logically grouped sequence of incremental git commits.
Executes GitHub operations via gh CLI wrapper. Use when managing issues, pull requests, workflows, CI runs, projects, releases, cache, labels, or searching repositories and code.
