git-workflow
Git best practices, branching strategies, commit conventions, and PR workflows. Use when reviewing git history, writing commits, setting up branching strategy, or improving git practices. Triggers on "git best...
发现 tools git workflows 相关 Skills,比较来源仓库和用途,查看适合你工作流的技能说明。
Git best practices, branching strategies, commit conventions, and PR workflows. Use when reviewing git history, writing commits, setting up branching strategy, or improving git practices. Triggers on "git best...
Apply Rules Repository conventions and forward-only workflow. Use when generating or editing docs, prompts, or code in projects that consume this repository or when this repository is the active workspace. Ensu...
Pull request best practices distilled from Graphite and GitHub guides. Use when creating pull requests in conjunction with the graphite-workflow skill to ensure they follow size guidelines, include proper conte...
Use this skill when working with Graphite (gt) for stacked PRs, when the user mentions pull requests, Graphite, stacking, or gt commands. Ensures proper use of gt commands instead of raw git for stack-aware ope...
Start a PR review inline comments fixing session. Use when users want to address, fix, or resolve inline review comments on a GitHub PR. Fetches unresolved comments and helps fix each one systematically.
Git 커밋 및 PR 생성 가이드. 사용자가 커밋, commit, PR, pull request 생성을 요청할 때 자동으로 활성화됩니다. 보안 검증을 통해 민감 정보 유출을 방지합니다.
새 작업 요청 시 기존 작업과의 맥락 유사성을 판단하고, 비유사한 경우 자동으로 git worktree를 생성하여 새 브랜치에서 작업합니다. 작업 시작, 새 기능 구현, 다른 이슈 작업 시 자동 활성화됩니다.
Git version control operations for repositories.
Use before starting implementation - research repository documentation, codebase patterns, and external resources to inform the approach
Use at the beginning of every work session - establishes context by checking GitHub project state, reading memory, verifying environment, and orienting before starting work
Use after completing implementation - create pull request with complete documentation, proper labels, linked issues, and verification summary
Defines context handover format when workers hit turn limit. Posts structured handover to GitHub issue comments enabling replacement workers to continue seamlessly.
Use before any code changes - hard gate ensuring work never happens on main branch, with proper feature branch creation from correct base
Use when committing code - ensures atomic, descriptive commits that leave the codebase in a merge-ready state at every point
Use to keep GitHub Project fields synchronized with actual work state - updates status, verification, criteria counts, and other project-specific fields
Use before starting ANY work - hard gate ensuring a GitHub issue exists, creating one if needed through user questioning
Use when encountering merge conflicts - handle conflicts cleanly, verify resolution, and maintain code integrity
Use to spawn isolated worker processes for autonomous issue work. Uses Task tool with run_in_background for parallel execution and TaskOutput for monitoring. Pre-extracts context to minimize worker token usage.
Use when a review finding cannot be fixed in current PR - creates properly documented tracking issue with full context, linked to parent, following full issue-driven-development process
MANDATORY before any GitHub project operations - caches project metadata to prevent rate limit exhaustion. Called by session-start. Other skills MUST use cached data.
Use after implementing features - 7-criteria code review with MANDATORY artifact posting to GitHub issue; blocks PR creation until complete
Use for any development work - the master 13-step coding process that orchestrates all other skills, ensuring GitHub issue tracking, proper branching, TDD, code review, and CI verification
Use during all development - no TODOs, no FIXMEs, no "we'll add this later"; do it now or get explicit deferral permission
Use throughout all work - ensures GitHub issues are updated continuously as work happens, not batched at the end
默认按已收录数据中的 GitHub 仓库 Stars 排序。Stars 属于来源仓库,同一仓库的多个技能可能共享相同数值;它反映仓库关注度,不代表单个技能的安装量或质量评分。