স্কিল খুঁজুন
আপনার এজেন্টের জন্য উপযুক্ত সক্ষমতা খুঁজে নিন।
safe-commit
git commit を行う際に自動発動。禁止ディレクトリ（ai/, .serena/）のコミット防止と、論理的なコミット分割を支援する。
notes-worktree
This skill should be used when the user asks to "set up notes worktree", "create documentation branch", "separate docs from code", "keep markdown in separate branch", "symlink documentation", "move docs to separate branch", or discusses keeping markdown files in a separate git branch while maintaining access via symlinks in the main project.
go-core
Core Go development patterns and idioms. Use for package design, code organization, configuration patterns, interface definitions, or when editing .go files. Triggers: package structure, dependency hierarchy, interface contracts, config transformation, encapsulation, layered organization, parameter encapsulation, modern Go idioms.
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
write-skills
Create or update SKILL.md files for this repo. Use when authoring skills in .claude/skills/.
task-breakdown
Break work into trackable tasks and maintain TODO.md. Use when starting features, bug fixes, or complex tasks. Always update TODO.md after completing work.
repo-release-guardrails
Protect against wrong-repo edits and enforce production parity assumptions.
gh-pr-review
GitHub PR review operations (inline comments, pending reviews, thread resolution)
commit-messages
Conventional Commits formatting guide for creating standardized commit messages. Use when Claude needs to create git commits, ensuring consistent message format with type prefixes (feat, fix, docs, chore). Automatically applied during git commit operations to maintain repository history standards.
git-github
Flutter 项目的 Git 和 GitHub 操作，包括分支管理、提交、推送、创建仓库、Pull Request、合并流程。当用户提到"git"、"github"、"提交"、"推送"、"分支"、"PR"、"合并"、"仓库"、"rebase"时使用此 skill。
init-risk-knowledge
Initialize the risk knowledge base repository by removing sample data and creating a clean structure. Use when setting up this repository for a new project. Creates .examples/ directory with sample files for reference while cleaning the main structure. This is a one-time operation for initial project setup.
pr-attribution
Shows who will be attributed to the changes in your PR by analyzing commit authors and line-by-line changes. Use when the user asks who will be credited for changes, who authored the PR changes, or when syncing with main causes unexpected authors to appear.
squash-commits
Squash all commits in a feature branch into a single commit with an AI-generated summary message. Use when the user wants to clean up their git history before merging, combine multiple commits, or create a single commit from a feature branch.
commit-message
Generates conventional commit messages based on pending git changes using standard source control terminology and best practices
resolve-pr-comments
Resolve bot review comments (CodeRabbit, Copilot, Gemini) on GitHub PRs using subagents. Use when: (1) User asks to 'review PR comments' or 'resolve PR comments', (2) User says 'work through PR N comments' or 'handle bot comments', (3) Need to triage CodeRabbit/Copilot/Gemini review comments, (4) Processing PR feedback at scale, (5) Want to see what's already fixed vs still pending. NOT for: creating PRs, reviewing code yourself, writing new reviews. Triggers: review PR comments, resolve PR comments, work through PR comments, handle bot comments, process CodeRabbit comments, triage PR feedback, fix PR review issues, resolve bot comments, pr comment resolver.
pr-code-review-fixer
Systematically fetch, analyze, and fix code review issues from GitHub Pull Requests. Use when the user asks to review and fix code issues from AI code reviewers (like Gemini Code Assist, GitHub Copilot, CodeRabbit) or any PR review comments. Fetches all review comments using gh CLI, attempts to fix all reported issues, commits changes to the PR branch, and generates a comprehensive fix report. Triggers on requests like "fix PR review issues", "address code review feedback", "apply review suggestions", or when given a GitHub PR URL with review comments to address.
create-github-issue
Research a bug, improvement, or feature request thoroughly, ask clarifying questions, then create a detailed GitHub issue with acceptance criteria.
