আপনার এজেন্টের জন্য উপযুক্ত সক্ষমতা খুঁজে নিন।
Performs interactive rebases with smart commit management and conflict resolution. Use when rebasing branches, cleaning up commit history, resolving conflicts, or when the user mentions "rebase", "interactive rebase", "squash commits", or wants to update their branch with latest changes from main/develop.
Manage git worktree lifecycle for parallel development. Create worktrees with port isolation, manage multiple branches simultaneously, clean up worktrees. CRITICAL: Use /create_worktree command, never manual git worktree commands. Ports auto-calculated to avoid conflicts.
Analyze repository structure and generate comprehensive index. Use to understand codebase organization or create repo-index.md.
Create isolated git worktrees for reviewing PRs, branches, tags, or commits without affecting main working directory.
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.
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.
Follow these patterns when implementing governance operations (copy, branch, transfer, promote, merge) in OptAIC. Covers artifact handling, RBAC mutations, lineage tracking, and activity emission.
Review code changes for AI-generated patterns, anti-patterns, and project convention violations. Use before committing or when reviewing PRs.
Manages the lifecycle of Git worktrees for parallel development tasks. Handles creation, safe removal, and branch management to keep the main working directory clean.
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.
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.
Use when creating git commits. Defines conventional commit format and message structure guidelines.
Instructions for committing changes to config files in the home directory using the dotfiles bare git repo.
A skill used when users request to write a commit message.
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
C++ development guidelines for modern C++17/20 projects. Use when creating C++ classes, functions, headers, or working with CMake, templates, smart pointers, RAII, memory management, STL containers, multithreading, or C++ best practices. Covers project structure, modern C++ idioms, build systems, testing with GoogleTest/Catch2, and performance considerations.
変更をコミットし、リモートにプッシュし、プルリクエストを作成します。ユーザーが「コミットしてPR作成」「変更をプッシュしてPR」などと指示した際に使用します。
Load when starting work in 10x-Mapmaster or when unsure about project standards. Covers file organization, naming conventions, type constraints, SQL style, and project-specific limits (200-char descriptions, answer enums). Use to understand how the codebase is structured and what standards to follow.
