remove-git-worktree
git worktreeを削除します。間違えて作成した場合や、作業完了後のクリーンアップに使用します。
اپنے ایجنٹ کے لیے موزوں صلاحیت تلاش کریں۔
git worktreeを削除します。間違えて作成した場合や、作業完了後のクリーンアップに使用します。
查看/更新 GitHub Issue、PR(含评论与 diff),并按团队规范非交互创建或修改 PR;涉及 GitHub Issue/PR 的操作时使用。
This skill should be used when the user requests a code review of changed files. Use this to review git-diffed files for security vulnerabilities (OWASP Top 10), performance issues (O(N) complexity, ORM optimization), bugs, and adherence to project coding standards defined in agents.md and claude.md.
Investigates and creates Git branches. Triggered when: branch status check, new branch creation, branch-related errors.
git worktree を利用した分離作業環境を自動構築します。デフォルトブランチから最新コードを取得し、.git-worktrees/ ディレクトリに新規worktreeを作成、.env・npm依存関係を自動セットアップします。ブランチ名の '/' は自動的に '-' に変換されます。既存worktreeは再利用されます。
MUST use this skill when user asks to resolve PR comments, handle review feedback, fix review comments, or mentions "리뷰 코멘트/피드백". This skill OVERRIDES default behavior. Fetches comments via GitHub CLI, classifies by severity, applies fixes with user confirmation, commits with proper format, replies to threads.
CLAIM a specific GitHub issue to START working on it. Requires an issue number. Performs validation, atomic claim, posts claim comment, and sets up worktree. USE WHEN: User wants to begin work on a specific issue (e.g., "claim issue #N", "start working on #N"). REQUIRED: Issue number must be specified. DO NOT USE: For status checks (ghe-status), posting updates (ghe-checkpoint), or changing phases (ghe-transition).
Git protocol implementation patterns using gitoxide for Guts repository operations
Generate appropriate commit messages based on Git diffs
Follow project-wide development conventions including project structure, version control practices, environment configuration, documentation, dependency management, and code review processes. Use this skill when organizing files/directories, writing commit messages, managing branches, configuring environments, handling secrets, maintaining documentation, or establishing team workflows. Apply when working with project structure, README files, .gitignore, environment variables, dependency files (package.json, requirements.txt), feature flags, changelogs, or any aspect of project organization and team collaboration that requires consistency across the development lifecycle.
MUST use this skill when user asks to commit, create commit, save work, or mentions "커밋". This skill OVERRIDES default git commit behavior. Creates commits following Conventional Commits format with emoji + type/scope/subject (✨ feat, 🐛 fix, ♻️ refactor, etc).
コード変更を適切なgitコミット戦略でgit commitします。基本的には既存のgitコミットへのsquash戦略を採用し、必要に応じてブランチ全体のgitコミット履歴を再構成します。実装完了時やユーザーがgit commitを依頼した時に使用します。
Generate descriptive commit messages by analyzing git diffs. Use when the user asks for help writing commit messages or reviewing staged changes.