agent-ops-git-worktree
Manage git worktrees for isolated development. Create, list, remove, and work in worktrees.
Discover Blockchain skills, compare source repositories and read the instructions for each workflow.
Manage git worktrees for isolated development. Create, list, remove, and work in worktrees.
Save and structure a voice idea to the knowledge base with automatic GitHub merge
GitHub issue structure and naming conventions for the project
Manage git operations safely. Includes stale state detection, branch/commit management. Never pushes without explicit user confirmation.
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement...
Troubleshoot GitHub Actions failures when creating branches or pull requests (GITHUB_TOKEN permissions, org policies, GH_PR_TOKEN fallback).
Create a safe checkpoint git commit on the current branch (avoid competition data, runs, artifacts, secrets).
Commit documentation changes to git after reviewing and confirming.
Initialize a new project with deep context gathering and PROJECT.md
Standardized branch creation with type detection, issue ID extraction, and worktree setup. Creates working branches (-WB) and integrates with selective-copy for clean PRs.
Pull Request作成を自動化します。lint→test→commit→PR作成まで。
Development: Git LFS file management for large binary files in the repository. Handles checkout, status, fetch, and verification of LFS-tracked files. Run from repository root with 'just lfs'. Use when develope...
GitHub CLI(gh)でリポジトリ/Issue/PR/Actions を操作する。issue作成・PR作成・チェック確認・ログ収集・Pages設定確認など、CLIでGitHub作業を進めたい時に使う。キーワード: gh, GitHub CLI, issue, pr, actions, workflo...
変更内容から適切にファイルを分割ステージし、読みやすいコミットメッセージでコミットする。conventional commits風の粒度調整、コミット前チェック(lint/build)を伴う作業で使う。キーワード: git commit, commit message...
Groom GitHub issues from needs-details to ready
Read, write, and merge iterate configuration from global and project files
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement...
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement...
Create comprehensive commit message from spec phases and commit all changes
Generate comprehensive PR descriptions following repository templates
manage branches and full pull request lifecycle, from creation to merge
Creates well-formatted GitHub issues when Claude needs human input. Use when uncertainty is high or decisions require human judgment.
デフォルトブランチを最新化して不要なローカルブランチを削除
Commits code to the repository. Use when the user asks "commit", "commit the code" or "commit the changes" or "commit the changes to the repository"
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.