b

Create a conventional commit message by analyzing staged changes

Expert GitHub PR manager that creates, updates, and manages pull requests. Auto-invoked when user says 'create PR', 'update PR', 'do PR', or similar PR-related commands.

Use this agent when you need to create, modify, or review REST API endpoints in a Laravel application. This includes designing RESTful routes, implementing controller methods, handling request validation, creating API resources, implementing authentication/authorization, and ensuring proper HTTP status codes and response formats. The agent excels at following Laravel conventions and best practices for API development. Examples: <example> Context: User needs to create a new REST endpoint for managing products in their Laravel application. user: "I need an endpoint to create new products with validation" assistant: "I'll use the laravel-rest-architect agent to design and implement a proper REST endpoint for product creation." <commentary> Since the user needs a REST endpoint in Laravel, use the Task tool to launch the laravel-rest-architect agent to create a properly structured endpoint with validation. </commentary> </example> <example> Context: User has just written a REST controller and wants it reviewed. user: "I've created a UserController with CRUD operations, can you check if it follows best practices?" assistant: "Let me use the laravel-rest-architect agent to review your REST controller implementation." <commentary> The user has written REST endpoints and wants them reviewed, so use the laravel-rest-architect agent to analyze the code for Laravel and REST best practices. </commentary> </example> <example> Context: User needs help with API versioning strategy. user: "How should I version my API endpoints?" assistant: "I'll engage the laravel-rest-architect agent to provide guidance on API versioning strategies in Laravel." <commentary> API versioning is a key REST API concern, use the laravel-rest-architect agent for expert guidance. </commentary> </example>

Use this agent when you need to generate commit messages that accurately describe code changes while adding a touch of dark humor and emotional depth. This agent excels at analyzing PHP code changes and crafting commit messages that are both technically precise and emotionally evocative. Examples: <example>Context: The user has just written a new PHP function and wants a commit message. user: "I just added a new caching mechanism to improve performance" assistant: "I'll use the melancholic-commit-writer agent to create a commit message for these changes" <commentary>Since the user needs a commit message written, use the Task tool to launch the melancholic-commit-writer agent to analyze the changes and write an emotionally-tinged but technically accurate commit message.</commentary></example> <example>Context: The user has fixed a bug in their PHP application. user: "Fixed the database connection issue that was causing timeouts" assistant: "Let me use the melancholic-commit-writer agent to craft a proper commit message for this fix" <commentary>The user has made a bug fix and needs a commit message, so use the melancholic-commit-writer agent to create one with its signature emotional style.</commentary></example>

Use this agent when you need to migrate code, APIs, or systems from one approach to another while maintaining backwards compatibility. This includes refactoring legacy systems, updating deprecated APIs, transitioning between frameworks or libraries, implementing versioning strategies, or planning major architectural changes that require careful migration paths. The agent excels at creating migration plans, writing compatibility layers, and ensuring comprehensive test coverage during transitions. Examples: <example> Context: User needs to migrate from an old API version to a new one user: "We need to update our payment processing from Stripe API v1 to v3" assistant: "I'll use the refactorer agent to help plan and implement this API migration while maintaining backwards compatibility" <commentary> Since this involves migrating between API versions, the refactorer agent is perfect for ensuring a smooth transition with proper testing. </commentary> </example> <example> Context: User is refactoring a monolithic application user: "I want to extract the authentication module from our monolith into a microservice" assistant: "Let me engage the refactorer agent to design a migration strategy that maintains compatibility during the transition" <commentary> This architectural change requires careful planning to avoid breaking existing functionality, making the refactorer agent ideal. </commentary> </example> <example> Context: User needs to update deprecated dependencies user: "Our app uses jQuery 1.x and we need to move to vanilla JavaScript" assistant: "I'll use the refactorer agent to create a phased migration plan with comprehensive testing" <commentary> Migrating away from a major dependency requires expertise in maintaining functionality while transitioning, which the refactorer specializes in. </commentary> </example>

Audit and trim AGENTS.md files by testing which facts AI agents can discover from code alone. Use when asked to lint, audit, optimize, prune, or trim AGENTS.md (or similar agent instruction files) in any repository. Removes redundant documentation that wastes context tokens.

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 when writing any plan document — project plans, PRDs, proposals, implementation plans, or design docs. Applies as a writing style layer alongside other planning skills like superpowers:writing-plans.

Use when writing, editing, or reviewing any SQL — including inline queries in PHP adapters, migration DDL, or raw SQL files. Enforces project SQL formatting conventions.