code-review-checklist
Apply when reviewing pull requests, conducting code reviews, or self-reviewing code before submission.
Discover tools git workflows skills, compare source repositories and read the instructions for each workflow.
Apply when reviewing pull requests, conducting code reviews, or self-reviewing code before submission.
Review pull requests using GitHub CLI. Invoke with /review-pr
Generate and update PR description on GitHub based on changes
Remove AI-generated code slop from the current branch
Perform elite PR review with confidence scores and post to GitHub
Generate Conventional Commit messages by analyzing git diffs. Use when committing code changes, when the user needs to write commit messages, or after staging changes.
Builds and manages open source Python library communities including CONTRIBUTING.md, CODE_OF_CONDUCT.md, issue/PR templates, contributor recognition, and GitHub automation. Use when setting up community infrast...
사용자가 '커밋해줘', 'commit', '/commit' 등 커밋을 요청할 때 사용. 레이어별/기능별 커밋 분리 원칙과 메시지 형식을 따름.
Provides comprehensive project folder structure design guidelines and best practices. Defines standard directory organizations for diverse project types including monorepos, web frameworks, backend services, li...
Create git commit messages based on current staged changes. Has support for git emoji messages.
Transforms repositories into structured plain-text digests optimized for LLM consumption. Use when analyzing GitHub repositories, digesting codebases, or ingesting git repos for AI analysis.
Provides Universal Standard for TDD, Security, and Code Quality. PROACTIVELY Use when writing code, debugging errors, or reviewing PRs. Modes: debug, review, refactor, implement.
GitHub Issue を修正するスキル。 以下の状況で使用: (1) ユーザーが「Issue #XX を修正して」と依頼した時 (2) ユーザーが明示的に「/gh-issue-fixer」を実行した時 (3) GitHub Issue の対応を求められた時
Review code changes in GitHub pull requests or local git branches against main branch. This skill should be used when users request code review for PRs or branch changes in git repositories.
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs
Use when starting feature work that needs isolation from current workspace or before executing implementation plans
Manage dotfiles configuration with bidirectional sync between local environment and ~/.dotfiles repository. Understand the automation script, configuration structure, and common commands.
Meta-orchestrator for managing ~/.claude as a private git repository with automatic versioning, branch orchestration, and DAG-based issue tracking. Use when initializing the config repo, committing configuratio...
Git expert for atomic commits, rebasing, and history management. Use when committing changes, managing git history, rebasing branches, or investigating when/where specific changes were introduced.
Git-native issue tracking with first-class dependency support. Issues stored alongside code in .beads/ directory, dual-persisted in SQLite (queries) and JSONL (git-friendly history). Hash-based IDs, DAG depende...
Convert arbitrary codebases into structured Obsidian wikis with human-in-the-loop iterative refinement. Use when user asks to analyze, document, or create a wiki for a codebase. Supports three modes: Fresh wiki...
Deliver a specific GitHub issue end-to-end
Gitコミットメッセージの作成ガイドライン。コミット作成時、`git commit`実行時、またはユーザーがコミットメッセージの書き方について質問した際に使用する。日本語でのコミットメッセージ作成ルールを提供。
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.