Find the perfect capability for your agent.
Execute comprehensive code reviews using OpenAI Codex CLI. Use when: (1) reviewing git commits by ID or range, (2) reviewing pull requests by number, (3) requesting thorough code quality analysis. Triggers on phrases like "codex review", "review commit", "review PR", "レビュー". Requires codex CLI to be installed and authenticated.
Manage git worktrees for the current repository. Use when asked to create a worktree, set up parallel development, work on multiple branches simultaneously, or manage existing worktrees. Triggers on phrases like "create worktree", "new worktree", "parallel branch", "list worktrees", or "remove worktree".
Commit current work to feature branch with Beads metadata tracking and git integration. MUST BE USED for all commit operations. Handles Feature-Key trailers, Beads status updates, and optional quick linting before commit. Use when user wants to save progress, commit changes, prepare work for review, sync local changes, or finalize current work, or when user mentions "uncommitted changes", "git status shows changes", "Feature-Key missing", commit operations, saving work, git workflows, or syncing changes.
Use when investigating test suite issues, reducing CI/CD time, identifying brittle tests, finding test duplication, or analyzing test maintenance burden - reveals test code quality problems through git history analysis
A skill to set up and manage a working directory for development tasks
Merge feature branch to main with pre-merge checks, CHANGELOG and ARCHITECTURE updates. Use when all spec stages are complete and user wants to merge. Ensures quality gates pass before merge.
Create atomic commits grouped by logical features with README.md and CLAUDE.md awareness.
When editing KINTSUGI notebook modules (Kdecon, Kstitch, Kreg, etc.), always edit the main repo first then sync to project folders
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.
Update and clean up project documentation files (primarily .ai/features/, but also README.md, PROGRESS_TRACKER.md, CLAUDE.md, and other .md files). Use when user requests documentation cleanup, organization, or updates for any feature, module, or project documentation (e.g., 'update photo viewer docs', 'clean up README', 'organize documentation'). Removes code snippets, outdated details, and redundant information while preserving essential architectural decisions and technical context.
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..
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을 요청했을 때 사용한다.
GitHub Pull Request review operations using gh CLI. Extract PR info, view diffs with line numbers, retrieve and post comments, create inline comments, and reply to comments. Use when reviewing PRs, conducting code reviews, or performing PR operations.
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
Installs a Git safety guard hook for Claude Code to prevent destructive Git and filesystem commands. Blocks accidental data loss from commands like 'git checkout --', 'git reset --hard', 'git clean -f', 'git push --force', and 'rm -rf'. Use this skill to set up safety rails in a new or existing repository, or globally for the agent.
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.
