git-master
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.
Essential command-line tools and system utilities.
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.
Use this agent when you need to review code changes in a pull request or after writing/modifying code. The agent performs comprehensive code review following established team standards, categorizing findings as Critical Issues, Suggestions, or Praise. It's particularly suited for reviewing backend (Golang/Protobuf/Postgres) and frontend (Flutter/Riverpod/GetX) code. Examples: <example> Context: After implementing a new API endpoint user: "I've added a new user profile update endpoint" assistant: "I'll review the code changes for the new endpoint" <commentary> Since new code was written, use the flutter-reviewer agent to ensure it meets quality standards. </commentary> assistant: "Let me use the flutter-reviewer agent to review this implementation" </example> <example> Context: After modifying database schema user: "I've updated the schema to add a new column to the users table" assistant: "I'll review these database changes" <commentary> Database schema changes require careful review for backward compatibil
Generate descriptive commit messages by analyzing git diffs. Use when the user asks for help writing commit messages or reviewing staged changes.
GitHub REST APIのSub-issue関連バグを回避するためのGraphQL API共通処理(Sub-issue登録、エラーハンドリング)を提供
Automatically review code changes for quality, best practices, TypeScript compliance, React/Next.js patterns, and project-specific conventions. Use before commits, after significant changes, or before pull requests. Checks code style, component patterns, error handling, testing, security, and Turkish language support.
Generate a .gitignore file for any project using the gitignore.io command-line tool (gi) or API.
Reusable git workflow for creating branches, commits, and pull requests. Handles branch naming with initials, commit creation with pre-commit hook handling, and PR generation.
Use when setting up git workflows for Claude Code - installs pre-commit hooks, commit templates with Claude attribution, PR templates, branch naming helpers, and Claude-specific gitignore entries
Creates comprehensive GitHub project documentation including README, CONTRIBUTING, CODE_OF_CONDUCT, CHANGELOG, architecture docs, and API documentation. Analyzes codebase to generate accurate, well-styled documentation with modern GitHub aesthetics. Use when setting up a new project, improving existing documentation, or generating missing docs.
Review code changes for quality, security, performance, and maintainability. Use when reviewing PRs, diffs, or code files. Provides structured feedback with severity levels.
Comprehensive code review with best practices, security, and maintainability checks. Use when reviewing pull requests, pre-commit code checks, learning code review techniques, improving code quality, or performing security audits. Triggers include "code review", "review code", "PR review", "pull request review", "security review", "code quality", or when evaluating code for issues and improvements.
Delegates code review to OpenAI Codex CLI. Use when user says "코드 리뷰해줘", "Codex한테 리뷰 맡겨", "PR 검토해줘", "코드 품질 체크", "리팩토링 제안해줘", "second opinion", or asks for code review, refactoring suggestions.
Quick 2-phase workflow for trivial changes - typos, colors, config updates (5-15 min)
Expert at crafting clear, meaningful git commit messages following conventional commit standards and repository conventions. Use when user asks to create commit messages, write commits, or needs help with git commit text. Analyzes git diffs and repository history to generate contextual, well-structured commit messages.
Use this skill after code changes are made, when reviewing implementations, checking code quality, or ensuring constitutional compliance. Apply when user mentions reviewing, analyzing, or checking code quality. Also use proactively after significant code implementations to verify they follow mini_agent framework principles.
Conventions for GitHub repo locations, forks, and open source contribution boundaries.
Systematically fetch, analyze, and fix code review issues from GitHub Pull Requests. Use when the user asks to review and fix code issues from AI code reviewers (like Gemini Code Assist, GitHub Copilot, CodeRabbit) or any PR review comments. Fetches all review comments using gh CLI, attempts to fix all reported issues, commits changes to the PR branch, and generates a comprehensive fix report. Triggers on requests like "fix PR review issues", "address code review feedback", "apply review suggestions", or when given a GitHub PR URL with review comments to address.
Manages git worktrees including listing, creating, removing, and switching between worktrees. Use when the user mentions creating worktrees, create a work tree, create worktree, new worktrees, parallel branches, or working on multiple branches simultaneously.
Generate descriptive commit messages by analyzing git diffs. Use when the user asks for help writing commit messages or reviewing staged changes.
Generate clear, conventional commit messages following project rules. Use when creating commits, writing commit messages, or reviewing staged changes.
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.
Create, amend, and manage Git commits with gh CLI including status checks and commit message validation
Iteratively, commit atomic changes to the respository. Use when the user or agent needs to autonomously commit atomic changes to the repository. Employs the "git-add", "git-message", and "git-status" in skills in sequence to perform the commit.