splitting-commit
Split large changes into logical commits by semantic meaning. Use when handling large features or refactors that should be split into focused commits.
Split large changes into logical commits by semantic meaning. Use when handling large features or refactors that should be split into focused commits.
Create a git commit following the project's gitmoji workflow with verification. Use when (1) user wants to commit staged changes, (2) user invokes /commit command, (3) user asks to create a commit. Triggers on "commit", "git commit", "create commit", "stage and commit".
On a GitHub PR, post '@codex review' via gh, wait for Codex’s review, then iterate fix+push cycles until Codex approves / reports no P0/P1 findings.
Code review methodology. Use when reviewing code locally or preparing for a PR review.
Automate the complete GitHub issue lifecycle. Fetches all issues, prioritizes by importance and execution speed, implements fixes using TDD, creates PRs, monitors for reviews, handles feedback autonomously, and notifies when complete. Uses extensive subagent parallelization for context efficiency.
Follow Kent Beck's Tidy First principles by strictly separating structural changes from behavioral changes. Use when refactoring code, restructuring code, making structural changes without changing behavior, renaming variables/functions, extracting methods, separating concerns, preparing code for new features, or need to ensure structural and behavioral changes are in separate commits.
Resolve a GitHub issue from intake through fix, validation, and push using gh, local edits, XcodeBuildMCP, and git.. Use when Fixing a GitHub issue end-to-end using gh and local changes..
Formats git commit messages according to Conventional Commits specification. Use this when the user asks to commit changes or write a commit message.
Execute merge workflow with CI checking and context gathering. Use when merging a PR with full Linear and GitHub context. Handles CI polling, merge validation, execution, cleanup, and status updates. Triggered by /yux-linear-merge command.
Clean up local git branches marked as [gone] (deleted on remote but still exist locally). Use when the user wants to clean up stale branches, remove gone branches, or delete branches that no longer exist on remote.
Create isolated git worktrees with smart directory selection and baseline verification. WHEN: MUST use when needing isolated workspace for feature work. Invoke with "/using-git-worktrees" or "create worktree", "isolated workspace", "work on multiple branches". WHEN NOT: Simple single-branch work, quick fixes on current branch.
Core Go development patterns. Use when working with file structure, error handling, naming conventions, or package organization. Includes domain system file organization and repository query method naming. Triggers: errors.go, domain errors, file structure, constants, interfaces, structured logging, slog, naming convention, Err prefix, domain system. File patterns: internal/**/*.go, pkg/**/*.go
Maintain the repo devcontainer environment and related workflow files. Use when changing .devcontainer or environment setup scripts.
코드 변경 사항을 적절한 git 커밋 전략으로 git commit한다. 기본적으로는 기존 git 커밋에 squash 전략을 적용하며, 필요에 따라 브랜치 전체의 git 커밋 히스토리를 재구성한다. 구현 완료 시점이나 사용자가 git commit을 요청했을 때 사용한다.
Creates and manages git branches with enforced mriley/ prefix naming convention. Validates branch names, switches branches safely, and handles branch creation with proper base branch selection.
Use when the user asks to create a pull request or PR for their work - creates PR using available tools with clear, concise title and description following standard template
You are an expert user of git worktrees. You interact with git worktrees to implement tasks.
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Incremental development agent with TDD workflow. Use when implementing features one at a time, following test-driven development, making commits, or resuming development work.
Creates structured fix plans in standardized format for GitHub issue comments.
Follow project-wide development conventions including project structure, documentation standards, version control practices, environment configuration, and dependency management. Use this skill when organizing files and directories, writing README documentation, creating commit messages, managing environment variables, updating dependencies, or establishing code review processes. Apply this skill when ensuring consistent project structure (src/, components/, utils/, tests/), maintaining up-to-date documentation, using clear commit messages and feature branches, properly configuring environment variables without committing secrets, keeping dependencies minimal and documented, and implementing feature flags for incomplete work. This skill ensures the entire team follows predictable patterns for project organization, maintains comprehensive documentation for setup and architecture, practices good version control hygiene, manages configuration securely, and establishes clear workflows for testing and code review.