Script and automate repetitive tasks and workflows.
⚠️ MANDATORY - Automatically invoked by safe-commit. Runs language-specific linting, formatting, static analysis, and type checking. Treats linter issues as build failures that MUST be fixed before commit. Auto-fixes when possible. NEVER run linters manually.
Intelligently commit changes with a context-aware, auto-generated message that the user can approve or edit before committing. Does not push.
Use GitHub MCP for issue/PR context, diffs, reviews, and automations. Use when the task references PR/issue numbers, review requests, or requires repo metadata beyond local git.
Comprehensive review and update of the documentation hub. Analyzes recent code changes, detects drift, validates structure, and proposes specific updates to keep documentation synchronized with the codebase.
Gitコミットを作成する際のヘルパー。変更内容を分析し、Gitmoji付きのConventional Commits準拠のメッセージを生成します。ハンク単位での論理的な分割とリバート可能なコミットを推奨します。
Generate well-structured git commit messages following conventional commits format. Use when committing changes, creating commit messages, or when commit history needs improvement. Ensures commits are clear, descriptive, and follow project conventions.
Analyzes and refactors code changes in the current git working tree (staged, unstaged, or recent commits). Ensures changes follow best practices, coding standards, and maintain code quality. Use when the user asks to "review my git changes", "check what I changed", "refactor my changes", "ensure my changes are clean", or "review before commit".
Generate conventional commit messages automatically. Use when user runs git commit, stages changes, or asks for commit message help. Analyzes git diff to create clear, descriptive conventional commit messages. Triggers on git commit, staged changes, commit message requests.
Generate conventional commit messages from git diff. Triggers: generate commit message, write commit, conventional commit, commit message, what should I commit, describe my changes
Generate properly formatted Conventional Commits messages with Claude Code footer. Use when creating git commits, writing commit messages, or the user mentions "commit", "git commit", or wants to save changes.
Access plain text versions of GitHub content (diffs, patches, raw files) using GitHub's URL transformations. Use when users share GitHub URLs for PRs, commits, files, or gists and you need to analyze the actual content. Works for pull requests, commits, file blobs, comparisons, and gists.
Navigate, modify, and manage Luan's dotfiles repository from any directory. Use when adding or configuring development tools, updating shell/editor/terminal settings, creating cross-platform install scripts (macOS, Arch Linux, GitHub Codespaces), or understanding dotfiles organization. Repo is at ~/dotfiles.
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.
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.
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.
