pull-request
Creates and opens pull requests from unmerged changes. Use when user asks to open a PR, create a pull request, make a PR, submit a PR, or handle unmerged/staged/unstaged changes that need a PR.
Creates and opens pull requests from unmerged changes. Use when user asks to open a PR, create a pull request, make a PR, submit a PR, or handle unmerged/staged/unstaged changes that need a PR.
Verifica que no haya credenciales, secrets o archivos sensibles antes de pushear a GitHub. Busca API keys hardcodeadas, .env con valores reales, y valida .gitignore.
GitHub issue label configuration, label taxonomy, and workflow automation mapping for MoAI-ADK projects
Quick reference for common Git commands and workflows. Use when working with version control, committing changes, managing branches, or resolving Git issues. Covers daily Git operations, branching strategies, and troubleshooting.
Stage, commit, and push git changes with conventional commit messages. Use when user wants to commit and push changes, mentions pushing to remote, or asks to save and push their work. Also activates when user says "push changes", "commit and push", "push this", "push to github", or similar git workflow requests.
Generates clear commit messages. Use when tasked to commit any code.
Create isolated git worktree for feature development. Handles directory selection, gitignore verification, project setup, and baseline test verification. Use this skill when: - Starting feature work that needs isolation from current workspace - Before executing implementation plans on a new branch - Want to work on multiple branches/features simultaneously - User asks to "create worktree", "isolate this work", "separate branch" - Need clean baseline before starting major changes Safety: ALWAYS verify worktree directory is gitignored before creating. Process: Check directory → Verify ignored → Create worktree → Run setup → Verify baseline tests
Use when committing changes to git, before running commit commands, to ensure explicit file staging, verification, and PR-friendly commit message format
GitHub Issue の実装フェーズを支援するスキル。指定 Issue の「## Implementation Plan (Codex)」コメントを実装仕様として解釈し、必要なコード変更、コミット作成、Pull Request 作成までを行う。すでに当該 Issue に紐づく PR が存在する場合は新規 PR を作らず、PR のレビュー指摘(コメント/レビュー/Review Threads)を収集して修正方針を提示し、同一ブランチへ追加コミットして PR を更新する。計画が存在しない/不十分な場合は実装せずユーザーに確認する。
Creates GitHub issues using gh CLI. Use when creating new issues.
This skill should be used when the user asks to "resolve merge conflicts", "fix git conflicts", "merge branches", or when autonomous-dev encounters merge conflicts during branch integration. Intelligently resolves git conflicts or escalates to user when uncertain.
Creates isolated git worktree environments for parallel development. Fetches latest from default branch, creates worktree in .git-worktrees/, copies .env and .serena files. Branch '/' is converted to '-'. Use when starting new features or switching context.
Use when making a new git commit, amending an existing commit, or when user asks to commit changes - enforces conventional commit format with type, scope, and description
Generates Conventional Commits messages, then commits changes. Use when the user says "commit", "git commit", or asks to commit changes, wants to create a commit, or when work is complete and ready to commit.
Use tk to manage tickets and keep .tickets/ in sync with code changes.
Use when session starts with CLAUDE.local.md containing Vault project field - automatically loads vault index, enables dual-location routing (vault + local docs), style adaptation, and cross-location linking with GitHub URLs for Obsidian project documentation
Search GitHub - find code, issues, users, and repositories across GitHub using gh CLI
Submit a code review to GitHub via the GitHub API. Use this as the final step in a code review pipeline to post review findings to a PR.
GitHub Issueの作業を開始する。ブランチを作成してチェックアウト。「/issue-start 4」のように使用