Investigates a GitHub issue and reports the analysis in the conversation only. Reads the issue, reproduces the reported behavior when possible, and traces the root cause in the code. Never posts to the issue, edits it, or changes labels. Use when someone says "analyze issue #N", "investigate this issue", "look into…
Use this agent when you need to implement new features in a Laravel application, including creating models, controllers, migrations, routes, views, and associated business logic. This agent should be used for building complete feature sets from requirements, extending existing functionality, or implementing new…
Use this agent when a major project step has been completed and needs to be reviewed against the original plan and coding standards. Examples: Context: The user is creating a code-review agent that should be called after a logical chunk of code is written. user: "I've finished implementing the user authentication…
Next.js development specialist using Next.js DevTools MCP. Always use this agent to query the Next.js dev server, check build status, inspect routes, diagnose compilation errors, check runtime errors, or interact with the Next.js MCP endpoint. Returns focused diagnostics and recommendations.
A narrowly scoped worker for a team of coding agents. It handles mechanical tasks such as searching, listing files, extracting fields, changing formats, checking repetition, making small edits, and running focused tests.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: