Loading...
Loading...
Found 4,154 Skills
Manage and synchronize multiple Git repositories across workspace-hub. Use for bulk git operations, repository status checks, branch management, and coordinated commits across 26+ repositories.
Guides technical evaluation of code review feedback before implementation. Use when receiving PR comments, review suggestions, GitHub feedback, or when asked to address reviewer feedback. Emphasizes verification and reasoned pushback over blind agreement.
Guide for working in parallel with other agents. Use when another agent is already working in the same directory, or when you need to work on multiple features simultaneously. Covers git worktrees as the recommended approach.
Read this skill before making git commits
Kubernetes Cluster API v1.12. Covers clusterctl CLI, ClusterClass, GitOps integration. Scripts for health checks, backup, migration, linting. Templates: clusters, DR, Prometheus. Keywords: CAPI, clusterctl, kubeadm, cluster lifecycle.
Automated commit analysis and regression detection for AItrader. 自动化提交分析和回归检测。 Use this skill when: - Running regression checks after code changes (代码修改后运行回归检测) - Analyzing git commit history (分析 git 提交历史) - Using AI to analyze code changes (使用 AI 分析代码变更) - Checking if fix commits are still correctly applied (检查修复是否正确应用) - Before merging PRs (合并 PR 前) Keywords: commit, regression, analysis, git, fix, validation, AI, 提交, 回归, 分析
Run /check-docs, then create GitHub issues for all findings. Issues are created with priority labels and structured format. Use /fix-docs instead if you want to fix issues immediately.
Reviews documentation PRs and provides GitHub PR suggestions. Load when asked to review, suggest changes, or provide feedback on docs content. Covers MDX, frontmatter, style guide, components, and content accuracy.
Enforces using git stash before file deletion and prohibits direct rm/unlink commands. Use when deleting files, cleaning up codebase, or removing tracked/untracked files. MUST ALWAYS be applied when file deletion is needed.
Configures and manages Depot CI, a drop-in replacement for GitHub Actions that runs workflows entirely within Depot. Use when migrating GitHub Actions workflows to Depot CI, running `depot ci migrate`, managing Depot CI secrets and variables, running workflows with `depot ci run`, debugging Depot CI runs, checking workflow compatibility, or understanding Depot CI's current beta limitations. Also use when the user mentions .depot/ directory, depot ci commands, or asks about running GitHub Actions workflows on Depot's infrastructure without GitHub-hosted runners. NOTE: Depot CI is currently in beta with limited availability.
Bootstrap new projects with curated settings.local.json permissions, CLAUDE.md, and .gitignore. Detects project type (cloudflare-worker, vercel-app, node-generic, python, ops-admin) and generates grouped, commented permission presets. Also tidies existing messy settings files (removes leaked secrets, shell fragments, deprecated MCP refs, duplicate entries). Trigger with 'kickoff', 'new project', 'bootstrap', 'setup claude', 'tidy permissions', 'clean settings', or 'init project'.
Execution-type Core-Lite Git worktree skill (only supports help/init/do/check/merge). Default execution without parameters is init --new + do exec; high-risk commands are only permitted via the CLI latch --yes --i-am-maintainer; lock conflicts default to SAFE_NEXT=init --new. Execution commands only read route-bash/route-powershell.