linear-sync
Updates Linear issues based on project-status evidence. Use when asked to sync Linear with code evidence or update issue status.
发现 tools git workflows 相关 Skills,比较来源仓库和用途,查看适合你工作流的技能说明。
Updates Linear issues based on project-status evidence. Use when asked to sync Linear with code evidence or update issue status.
Strict Git workflow enforcer. Handles Conventional Commits, standard branching, and advanced recovery (revert/reset) without executing write commands.
Use when receiving code review feedback (especially if unclear or technically questionable), when completing tasks or major features requiring review before proceeding, or before making any completion/success c...
Git workflow management using Hug (enhanced Git replacement). Use for ALL Git operations. Triggers: commit, amend, staging, git status, git log, repo inspection, fixing commits. Use whenever Claude needs to: (1...
Expert-level Git repository investigation using Hug SCM tools for understanding code evolution, tracking down bugs, analyzing changes, and managing development workflows
Use when completing tasks, implementing major features, or before merging
Use when starting feature work that needs isolation from current workspace or before executing implementation plans
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
Use when merging parallel worktrees back together after parallel implementation
Use when git merge or rebase fails with conflicts, you see 'unmerged paths' or conflict markers (
Provides standardized Git workflows, commit message conventions, branching strategies, and collaboration patterns for all agents performing Git operations. Use when creating commits, choosing branching strategi...
面向 Jujutsu(jj) 版本控制的使用、工作流、revset/fileset 语法、Git 互操作与配置排错指导。用于解答 jj 命令与概念差异、迁移 Git 流程到 jj、处理冲突/回滚、配置与远程书签相关问题。
Generates and updates CHANGELOG.md files by analyzing git commit history. Handles both creating new changelogs and appending recent changes. Analyzes commits using conventional commit format and categorizes cha...
This skill should be used when the user asks to "analyze fix commits and generate postmortems", "create postmortems from git history", or "summarize bug fixes into postmortem reports".
Analyze git repositories and generate comprehensive markdown documentation for quick understanding. Use when user asks to "analyze this repo", "document the codebase", "explain how this project works", "generat...
Teaches when to use gabb_structure for efficient file exploration. Use gabb_structure before reading large files in supported languages.
Create high-quality git commits with conventional format, meaningful descriptions, and analysis of changes. Use when user asks to commit, stage changes, or prepare a commit message.
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
Execute Pull Request creation workflow including authentication, branch verification, change analysis, and gh CLI operations. Use when asked to create a PR, open a pull request, submit changes for review, or af...
Execute Git commits with proper workflow including authentication, branch safety, atomic commits, and style analysis. Use when asked to commit, save, or persist changes to Git, after completing tasks where comm...
Check GitHub API rate limit status and remaining quota. Use when the user asks about API quota, rate limits, or wants to know how many requests are remaining.
Get GitHub repository information including stars, forks, issues, languages, and metadata. Use when the user asks for repository details, GitHub stats, or repo information.
GitHub Pull Requestのレビュー操作を行うスキル。PR情報取得、差分確認、コメント取得・投稿、インラインコメント、コメント返信をghコマンドで実行する。PRレビュー、コードレビュー、PR操作が必要な時に使用。
Use when implementation is complete, all tests pass, and you need to integrate the work. Guides completion by presenting structured options for merge, PR, or cleanup.
默认按已收录数据中的 GitHub 仓库 Stars 排序。Stars 属于来源仓库,同一仓库的多个技能可能共享相同数值;它反映仓库关注度,不代表单个技能的安装量或质量评分。