mygentic-eng

Evaluate GitHub issue quality and completeness for agent implementation

Transform rough feature ideas into comprehensive implementation specifications

Generate a new custom Claude Code slash command from a description

Generate a high-quality GitHub issue optimized for agent implementation

Complete 3-phase automation: implement → review → merge for GitHub issues

Use this agent when you need to review Python code changes with an extremely high quality bar. This agent should be invoked after implementing features, modifying existing code, or creating new Python modules. The agent applies Andre's strict Python conventions and taste preferences to ensure code meets exceptional standards. Examples: - <example> Context: The user has just implemented a new FastAPI endpoint. user: "I've added a new user registration endpoint" assistant: "I've implemented the registration endpoint. Now let me have Andre review this code to ensure it meets our quality standards." <commentary> Since new endpoint code was written, use the andre-python-reviewer agent to apply Andre's strict Python conventions and quality checks. </commentary> </example> - <example> Context: The user has refactored an existing service class. user: "Please refactor the EmailService class to handle attachments" assistant: "I've refactored the EmailService to handle attachments." <commentary> After modifying existing code, especially services, use andre-python-reviewer to ensure the changes meet Andre's high bar for code quality. </commentary> assistant: "Let me have Andre review these changes to the EmailService." </example> - <example> Context: The user has created new utility functions. user: "Create a data validation module" assistant: "I've created the data validation module." <commentary> New modules should be reviewed by andre-python-reviewer to check Pythonic patterns, type hints, and best practices. </commentary> assistant: "I'll have Andre review this module to ensure it follows our conventions." </example>

Use this agent when you need to review TypeScript code changes with an extremely high quality bar. This agent should be invoked after implementing features, modifying existing code, or creating new TypeScript components. The agent applies Andre's strict TypeScript conventions and taste preferences to ensure code meets exceptional standards. Examples: - <example> Context: The user has just implemented a new React component with hooks. user: "I've added a new UserProfile component with state management" assistant: "I've implemented the UserProfile component. Now let me have Andre review this code to ensure it meets our quality standards." <commentary> Since new component code was written, use the andre-typescript-reviewer agent to apply Andre's strict TypeScript conventions and quality checks. </commentary> </example> - <example> Context: The user has refactored an existing service module. user: "Please refactor the EmailService to handle attachments" assistant: "I've refactored the EmailService to handle attachments." <commentary> After modifying existing code, especially services, use andre-typescript-reviewer to ensure the changes meet Andre's high bar for code quality. </commentary> assistant: "Let me have Andre review these changes to the EmailService." </example> - <example> Context: The user has created new utility functions. user: "Create a validation utility for user input" assistant: "I've created the validation utility functions." <commentary> New utilities should be reviewed by andre-typescript-reviewer to check type safety, naming conventions, and TypeScript best practices. </commentary> assistant: "I'll have Andre review these utilities to ensure they follow our conventions." </example>

Use this agent when you need to research and gather external best practices, documentation, and examples for any technology, framework, or development practice. This includes finding official documentation, community standards, well-regarded examples from open source projects, and domain-specific conventions. The agent excels at synthesizing information from multiple sources to provide comprehensive guidance on how to implement features or solve problems according to industry standards. <example>Context: User wants to know the best way to structure GitHub issues for their Rails project. user: "I need to create some GitHub issues for our project. Can you research best practices for writing good issues?" assistant: "I'll use the best-practices-researcher agent to gather comprehensive information about GitHub issue best practices, including examples from successful projects and Rails-specific conventions." <commentary>Since the user is asking for research on best practices, use the best-practices-researcher agent to gather external documentation and examples.</commentary></example> <example>Context: User is implementing a new authentication system in Rails and wants to follow security best practices. user: "We're adding JWT authentication to our Rails API. What are the current best practices?" assistant: "Let me use the best-practices-researcher agent to research current JWT authentication best practices, security considerations, and Rails-specific implementation patterns." <commentary>The user needs research on best practices for a specific technology implementation, so the best-practices-researcher agent is appropriate.</commentary></example> <example>Context: User is setting up a TypeScript project and wants to know best practices. user: "What are the best practices for organizing a large TypeScript React application?" assistant: "I'll use the best-practices-researcher agent to gather comprehensive information about TypeScript React application structure, including examples from successful projects." <commentary>The user needs research on TypeScript best practices, so the best-practices-researcher agent should gather modern TypeScript conventions.</commentary></example> <example>Context: User is implementing a Python API and wants to follow best practices. user: "What are the best practices for building a FastAPI application with SQLAlchemy?" assistant: "Let me use the best-practices-researcher agent to research FastAPI and SQLAlchemy best practices, async patterns, and project structure." <commentary>The user needs research on Python-specific best practices, so the best-practices-researcher agent is appropriate.</commentary></example>

Use this agent when you need a final review pass to ensure code changes are as simple and minimal as possible. This agent should be invoked after implementation is complete but before finalizing changes, to identify opportunities for simplification, remove unnecessary complexity, and ensure adherence to YAGNI principles. Examples: <example>Context: The user has just implemented a new feature and wants to ensure it's as simple as possible. user: "I've finished implementing the user authentication system" assistant: "Great! Let me review the implementation for simplicity and minimalism using the code-simplicity-reviewer agent" <commentary>Since implementation is complete, use the code-simplicity-reviewer agent to identify simplification opportunities.</commentary></example> <example>Context: The user has written complex business logic and wants to simplify it. user: "I think this order processing logic might be overly complex" assistant: "I'll use the code-simplicity-reviewer agent to analyze the complexity and suggest simplifications" <commentary>The user is explicitly concerned about complexity, making this a perfect use case for the code-simplicity-reviewer.</commentary></example>

Use this agent when you need to conduct a comprehensive design review on front-end pull requests or general UI changes. This agent should be triggered when a PR modifying UI components, styles, or user-facing features needs review; you want to verify visual consistency, accessibility compliance, and user experience quality; you need to test responsive design across different viewports; or you want to ensure that new UI changes meet world-class design standards. The agent requires access to a live preview environment and uses Playwright for automated interaction testing. Example - "Review the design changes in PR 234"