Loading...
Loading...
Found 2,779 Skills
Create a git commit with a clear, value-communicating message. Use when the user says "commit", "commit this", "save my changes", "create a commit", or wants to commit staged or unstaged work. Produces well-structured commit messages that follow repo conventions when they exist, and defaults to conventional commit format otherwise.
Debugging toolkit for AI agents. Diagnose symptoms via memory cache -> behavior cache -> codebase search, trace data flow, git-bisect bad commits, and compare output directories.
Install and update skills into the skill system from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, update existing skills, or install a skill from another repo (including private repos).
Structured git commit messages following Conventional Commits format for Go projects. Generates well-scoped, atomic commits with clear descriptions. Use when committing changes, writing commit messages, preparing PRs, or reviewing commit history quality. Trigger examples: "commit these changes", "create commit", "commit message", "prepare PR", "squash commits". Do NOT use for changelog generation (use changelog-generator) or code review (use go-code-review).
Create GitHub pull requests from the current branch with auto-generated titles, descriptions, reviewers, and labels. Use this skill whenever the user wants to create a PR, open a pull request, submit code for review, push changes for merge, or mentions "PR", "pull request", "code review", or "merge request". Also trigger when the user says things like "I'm done with this feature", "ready to submit", "open a draft PR", or "send this for review". Works with GitHub CLI by default, with guidance for GitLab and Bitbucket.
Crée, récupère, met à jour et gère les issues GitLab avec collecte complète du contexte. À utiliser quand l'utilisateur veut créer une nouvelle issue, voir les détails d'une issue, mettre à jour des issues existantes, lister les issues du projet ou gérer les workflows d'issues dans GitLab.
GitHub 审视 - Read-only GitHub triage for issues and PRs. 触发条件/Triggers: 需要分析 GitHub Issues 或 PRs、生成审查报告、或分类问题。 核心原则/Core Principles: - 只读不写/Read-only: 永不修改 GitHub 状态 - 证据支持/Evidence: 每个结论都需要 GitHub permalink 证明 - 并行分析/Parallel: 每个 Issue/PR 独立后台任务 - 报告输出/Reports: 写入临时目录，不操作 GitHub 命令/Commands: - /审视 analyze <repo> - 分析仓库所有开放 Issue 和 PR - /审视 issues <repo> - 只分析 Issues - /审视 prs <repo> - 只分析 PRs - /审视 <URL> - 分析特定 Issue 或 PR - /analyze <repo> - English command 能力/Capabilities: GitHub 数据读取、问题分类、证据收集、报告生成、后台并行处理。
Responds to unanswered GitHub discussions and issues with codebase-informed replies. Use when clearing community question backlog.
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
Use this skill when the user mentions phrases such as: "analyze a project", "analyze a repository", "analyze GitHub", "project analysis", "source code analysis", "architecture analysis", "code analysis", "learn this project", "research this framework", "see how this library is implemented", "compare two projects", "project evaluation", "framework evaluation"
Used when the user requests to search technical documents, look up code examples, check web resources or view GitHub repository information.
Split uncommitted changes into focused, logical commits using git-hunk. Use when asked to "split changes", "split commits", "organize commits", "commit by hunk", or "separate changes into commits".