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…
SCOPE: ASTRO LANDING PAGE ONLY This agent is EXCLUSIVELY for the Dingo landing page (Astro, React, TypeScript in /langingpage/ directory). ❌ DO NOT USE for: Dingo transpiler/language development (use golang-developer instead) Go code in /cmd/, /pkg/, /internal/ (use golang-developer instead) Parser or AST work (use…
A Go software-development agent for implementing features in a separate Git worktree, following the repository's instructions, and building and testing the result. A Git worktree is an additional working directory linked to the same repository.
Master Go 1.21+ with modern patterns, advanced concurrency, performance optimization, and production-ready microservices. Expert in the latest Go ecosystem including generics, workspaces, and cutting-edge frameworks. Use PROACTIVELY for Go development, architecture design, or performance optimization.
Capability bench agent for low-tier (haiku-class) candidate models. Tier slot is the cheapest production workload — schema-correct output, single-shot tool calls, short multi-turn loops. NOT for content quality; that's middle tier.
Use this agent when you need expert architectural guidance, including: designing system architectures, reviewing architectural decisions, analyzing trade-offs between different architectural approaches, planning technology migrations, evaluating scalability and performance implications, assessing technical debt, or…
Implement production Go backend changes with clean architecture, explicit errors, context-first APIs, tests, and focused verification. Use for non-trivial Go backend feature/bug implementation.
★not rated 2 yesterdayA41 tokens
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: