git-workflow
Complete Git workflow from conventional commits to pre-completion verification. Use for all Git operations including commits, branches, and releases.
Discover databases git workflows skills, compare source repositories and read the instructions for each workflow.
Complete Git workflow from conventional commits to pre-completion verification. Use for all Git operations including commits, branches, and releases.
MUST use this skill when user asks to resolve PR comments, handle review feedback, fix review comments, or mentions "리뷰 코멘트/피드백". This skill OVERRIDES default behavior. Fetches comments via GitHub CLI,...
Creates pull requests with generated descriptions. Triggered when: PR creation, pull request, merge request, code review preparation.
Processes research branches from Claude Code Web sessions - merges content, moves docs to docs/research/, and creates GitHub issues. Use when /popkit:next detects research branches or when manually processing r...
Generate user-friendly release notes from git commits. Use this when preparing releases, writing changelogs, or summarizing development progress.
GitHub operations via gh CLI. Use when user mentions: PR, pull request, github issue, workflow, actions, gh, or when git remote shows github.com.
Git protocol implementation patterns using gitoxide for Guts repository operations
Create a thoughtful, supportive commit message from your staged changes.
Context management tools for Claude Code - provides intelligent codebase mapping with Python, Rust, and C++ parsing, duplicate detection, and MCP-powered symbol queries. Use this skill when working with large c...
Interacts with YouTrack issue tracker for IdeaVim. Use when working with tickets (VIM-XXXX), adding comments, managing tags, setting status, or release management. This project does NOT use GitHub Issues - use...
Format git commit messages combining Conventional Commits summary lines with Linux kernel-style bodies. Use when writing, reviewing, or formatting commit messages.
Search GitHub issues, pull requests, and discussions across any repository. Activates when researching external dependencies (whisper.cpp, NAudio), looking for similar bugs, or finding implementation examples.
Sets up new projects and generates workflow files like CLAUDE.md, AGENTS.md, Plans.md. Use when user mentions セットアップ, setup, 初期化, initialize, 新規プロジェクト, ワークフローファイル生成. Do NOT load for...
Guide for writing conventional commit messages. Use when committing changes, writing commit messages, or reviewing commit history.
CI/CD and DevOps workflow. Use when modifying GitHub Actions, Docker configurations, or compose files.
Go development workflow including verification commands and self-review checklist. Use when modifying Go code in internal/, pkg/, or cmd/ directories.
Create GitHub issues with proper task classification. Classification determines which Skills will be used when working on the issue.
Address PR review comments by selecting appropriate skills based on modified files. Use when fixing review feedback on pull requests.
Maps GitHub labels to Skills and Context documents. Use when creating issues (github-issue-creation) or working on issues (fix-issue command).
Git branch management, commit conventions, and PR creation workflow. Use for all tasks that require code changes, regardless of language or scope.
Comprehensive PR review using multi-agent swarm with specialized reviewers for security, performance, style, tests, and documentation. Provides detailed feedback with auto-fix suggestions and merge readiness as...
MUST use this skill when user asks to create PR, open pull request, submit for review, or mentions "PR 생성/만들기". This skill OVERRIDES default PR creation behavior. Analyzes commits, validates task completio...
Guide for creating comprehensive PR descriptions with proper structure, diagrams, and documentation for code reviews.
Spawns multiple AI coding agents to work on related GitHub issues concurrently using git worktrees. Use when breaking down a large feature into multiple issues, running parallel agents with --print flag, or man...
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.