create-worktree
Git worktree を作成し、並行開発用の独立したブランチ環境を構築する。プラットフォーム固有コード開発時に使用。
feature-dev
Guía el desarrollo de nuevas features. Usar cuando se implementa funcionalidad nueva, se trabaja en issues de GitHub, se planifica arquitectura, o se crean PRs de desarrollo.
commit-push
git status / diff を確認し、Conventional Commits 形式でコミットしてプッシュするための手順。差分の断面を残したいときや一定量の修正がまとまったときに使用する。
ci-autofix-loop
End-to-end CI fixer loop for the current git branch/PR (GitHub Actions + Buildkite). Use when asked to “fix CI”, “make checks green”, or “address failing checks”, and the workflow should: (1) discover failing checks via `gh pr checks`, (2) diagnose failures via provider logs (Buildkite log tooling/API or `gh run view --log-failed`), (3) apply minimal code fixes, (4) run `code-simplifier` + `code-review`, (5) commit + push, and (6) iterate until remaining failures are unfixable via code change.
pr-conflict-resolution
Skill for resolving pull request merge conflicts in the Corrupt Video File Inspector project
git-commit-executor
Gitの変更を分析して論理的なコミット単位に分割し、Conventional Commits形式で実際にコミットを実行する。
treido-dev
Treido development workflow. Triggers on "TREIDO:" prefix. Use for daily tasks, picking next item from TODO, executing small changes (1-3 files), and running verification gates.
governance-patterns
Follow these patterns when implementing governance operations (copy, branch, transfer, promote, merge) in OptAIC. Covers artifact handling, RBAC mutations, lineage tracking, and activity emission.
writing-claude-md
Use when creating or updating CLAUDE.md files at any level (global, project, folder). Covers inheritance rules and token budgets.
git-workflow
gitを使用する際に使用。Conventional Commits、ブランチ命名、1機能1PRルールをカバー。
git-operations
Git操作に関する包括的なガイド。ユーザーがブランチ作成、コミット、プッシュ、プル、マージ、リベースなどのGit操作を実行したい場合や、Gitのベストプラクティスに従う必要がある場合に使用すべきスキルです。
git-worktree-manager
Manages the lifecycle of Git worktrees for parallel development tasks. Handles creation, safe removal, and branch management to keep the main working directory clean.
command-qa-checklist
Use the /qa-checklist slash command for QA and self-review before delivery. Use when: validating changes and tests.
gh-cli
Standardize all GitHub interactions via the GitHub CLI (`gh`) instead of ad-hoc URLs, UI clicks, or direct REST API calls. Use when you need to read or change GitHub state (repos, issues, pull requests, reviews, check status, Actions workflows/runs, releases, labels, milestones, discussions, gists) and want deterministic output (prefer `--json` + `--jq`). Also use when the user provides a GitHub URL, including deep links like `https://github.com/OWNER/REPO/pull/123`, `.../issues/123`, `.../pull/123/files`, or comment permalinks like `#issuecomment-...`, and you need to fetch the underlying PR/issue/thread and reply. Fall back to `gh api` only when there is no first-class `gh NOUN VERB` command.
pr-creation
This skill should be used when the user asks to "create a PR", "open a PR", "submit a PR", "raise a PR", "file a PR", "make a PR", "create a pull request", "open a pull request", "new PR", or any variation requesting GitHub pull request creation.
commit-conventions
Commit message style and structure for this repository.
issue-worker
Spawn a Claude worker to handle a GitHub issue. Fetches issue details, creates a feature branch, and works autonomously. Use when you want to delegate an issue to a worker.
write-commit-message
Use when creating git commits. Defines conventional commit format and message structure guidelines.
dotfiles-commit
Instructions for committing changes to config files in the home directory using the dotfiles bare git repo.
