receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement...
Discover blockchain git workflows skills, compare source repositories and read the instructions for each workflow.
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement...
Inspire team repository inventory and standards. Use when understanding the codebase structure or repository conventions.
Create a pull request following project PR guidelines and template. Use this when asked to draft or create a PR.
Resume work on existing feature clone
Tools for fetching GitHub PR/issue/commit comments cleanly via gh CLI. Use when needing to retrieve comment data from GitHub with structured JSON output.
Provides commands and patterns for Data Version Control (DVC). Use when the user asks about versioning large files, creating pipelines, or reproducing experiments.
Code review a GitHub pull request
A skill for reviewing software changes. It helps analyze differences between git references (branches, tags, commits), review history, and provide feedback to ensure code quality and adherence to project conven...
Enforces strict waterfall development workflow with phase gates. Use when (1) features.yml exists in project root, (2) user asks to implement/develop/build a feature, (3) user explicitly requests waterfall work...
Reference guide for glab commands covering issues, merge requests, pipelines, releases, and CI/CD—includes common workflows and syntax examples
ユーザーが「プッシュして」「公開して」「push したい」と言ったときに使う。プッシュ前にブランチと未プッシュコミットを確認するスキル。
현재 작업 내용을 커밋하고 PR을 생성한 후 코드 리뷰를 수행하고 피드백을 반영하여 머지하는 전체 워크플로우를 자동화합니다. 사용자가 "PR 만들어 줘", "커밋하고 PR 생성해 줘", "코드 리뷰 후 머지해 줘" 등의 요청을 할...
Reword or amend the current HEAD commit message in a Git repo. Use when the user asks to "reword git HEAD", "amend the last commit message", or "change the most recent commit message".
Generate user-friendly release notes from git commits. Use this when preparing releases, writing changelogs, or summarizing development progress.
Basic git operations for repository inspection. Use for git diff, git log, git status, git remote, and other read-only git commands.
Single source of truth for canonical VMs, canonical IDEs, and canonical trunk branch. Use this to keep dx-status, mcp-doctor, and setup scripts aligned across machines.
git diff를 분석하여 설명적인 커밋 메시지를 생성합니다. 사용자가 커밋 메시지 작성이나 스테이징된 변경사항 검토를 요청할 때 사용합니다.
Manage and resolve repository issues
Creates commits following Conventional Commits v1.0.0 specification. Use this when creating git commits with properly formatted commit messages.
Orchestrates git workflow for Python feature/release/hotfix development. Loads and coordinates other skills based on current context. Includes PR feedback handling via work-item generation. Use when: - User sa...
ForkLore 백엔드(Django/DRF) 개발 워크플로우 스킬. 이슈 기반 개발 + develop 브랜치 전략 + TDD(RED-GREEN-REFACTOR) + 서비스 레이어(views는 thin wrapper) + StandardJSONRenderer/camelCase API 규약 + drf-spectacular...
Manages git operations: worktree creation, branch management, commits, PRs, semantic versioning, daily rebase workflow, and PR feedback handling. Use when: Creating branches/worktrees, committing, pushing, ver...
git worktreeを削除します。間違えて作成した場合や、作業完了後のクリーンアップに使用します。
Update the active development session when work is completed. Use automatically after code changes, bug fixes, feature implementations, or file modifications when .claude/sessions/.current-session exists.
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.