code-review
This skill should be used when reviewing GitHub Pull Requests to provide comprehensive code quality, security, and architecture analysis with optional JIRA ticket integration.
Discover documentation automation tools skills, compare source repositories and read the instructions for each workflow.
This skill should be used when reviewing GitHub Pull Requests to provide comprehensive code quality, security, and architecture analysis with optional JIRA ticket integration.
Generate conventional commit messages following official Conventional Commits specifications https://www.conventionalcommits.org/en/v1.0.0/#summary. Use when asked to generate commit messages, to analyse change...
Generate descriptive commit messages by analyzing git diffs. Use when the user asks for help writing commit messages or reviewing staged changes.
커밋 메시지 생성 스킬. 다음 상황에서 자동 호출: - "커밋", "commit", "커밋 메시지", "커밋해줘", "커밋 부탁" - "변경사항 커밋", "staged 커밋", "git commit"
Ensures commits follow conventional commits, branch naming conventions, and PR templates. Use when creating commits, branches, or PRs, or when user mentions git workflow.
Inspire team repository inventory and standards. Use when understanding the codebase structure or repository conventions.
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...
TỰ ĐỘNG COMMIT VÀ PUSH CODE - AUTO COMMIT MESSAGE GENERATION ✅ LUÔN SỬ DỤNG SKILL NÀY KHI: - Người dùng yêu cầu commit code - Người dùng yêu cầu push code - Người dùng nói "lưu code lên git", "đẩy code lên gi...
Guide for breaking changes into logical, atomic commits using interactive staging. Use when committing changes that span multiple concerns, when needing to stage parts of files (hunks), when asked to create wel...
This skill should be used when the user asks to "generate repository documentation", "create a README", "document API", "write architecture docs", "add CONTRIBUTING guide", "update repo docs", "document codebas...
Git workflow conventions for RawDrive. Use when creating commits, branches, pull requests, or reviewing code changes.
Manage CodeCommit PRs (create/list/view)
Manages safe git branching, conventional commits, and push flow for Next.js + TS projects. Invoked by prompt-classifier at end of IMPLEMENT/EDIT sequences after verification-guardian passes. Ensures work happen...
This skill should be used when the user asks to "review this commit message", "validate my commit", "improve this commit message", "explain conventional commits", "teach me commit message best practices", "writ...
This skill should be used when the user asks to "review this commit message", "validate my commit", "improve this commit message", "explain conventional commits", "teach me commit message best practices", "writ...
This skill should be used when the user types "/review-commit" or asks to review and clean up staged changes before committing. It launches the commit-cleaner agent to review code quality, remove redundancies,...
Full PR review workflow with checklist verification and release notes. Use when reviewing PRs before merge.
Project structure and coding conventions for RawDrive. Use when creating new files, organizing code, or understanding the codebase layout. CRITICAL for preventing random file creation.
GitHub PR 제목과 본문을 자동 생성하고 코드리뷰까지 수행. "do it PR", "PR 작성", "풀리퀘스트" 키워드로 자동 활성화
Standardized patterns for Git branching, worktrees, and lifecycle management.
PR workflow, release notes, build management, and GitHub conventions. Use when creating PRs, writing commit messages, or preparing releases.
Automates the end-to-end Git workflow from committing to feature branch to merging via the GitHub CLI.
Addresses PR review comments systematically. Use when fixing review feedback, responding to code review threads, or processing PR comments.
Complete Git workflow from conventional commits to pre-completion verification. Use for all Git operations including commits, branches, and releases.
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.