pr-review-fix
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.
Discover blockchain git workflows skills, compare source repositories and read the instructions for each workflow.
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
Generates git patch files from codebase modifications for local application. Use when user mentions patch, diff, export changes, bring changes back, apply locally, or after editing uploaded codebases.
Mandatory inspection procedures for understanding Rails codebase structure before writing any code. Use this skill FIRST before any code generation task to discover existing patterns, conventions, dependencies,...
Mandatory inspection procedures for understanding Rails codebase structure before writing any code. Use this skill FIRST before any code generation task to discover existing patterns, conventions, dependencies,...
Merge a GitHub PR and clean up the worktree. Use when merging a PR from a feature branch worktree that meets merging criteria.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.