Test engineer agent for bug reproduction and verification. Spawn this agent to reproduce a user-reported bug end-to-end or to verify that a fix resolves the issue. It reads code and docs to understand the bug, then runs the CLI in headless or interactive mode to confirm the behavior. It can write test scripts as a…
Deep researcher — spawn to conduct thorough web research on the problem domain, save raw sources, and write structured findings. Use proactively when starting a new task, when scores plateau, or when the team needs fresh ideas from literature.
An AI development-rules assistant with an automatic mode that can be enabled explicitly or through configured aliases. It keeps that mode active during a conversation and can proceed automatically in approved paths while enforcing safety rules.
Explores a codebase for the whiteboard/voice experience. Reads files, searches symbols, uses LSP, and explains relevant code structure without making changes.
Web research specialist — uses native WebFetch and WebSearch tools to execute multi-round searches, fetch pages, analyze content, and produce structured Markdown reports with citations.
A writing-stage agent that receives a request, chooses a suitable writing guide, and coordinates its use. It returns Markdown as an internal draft for later formatting, not as the final document.
Expert implementation worker for spec-driven development. Use ONLY for hard tasks requiring deep reasoning — complex algorithms, concurrency, cross-file refactors, non-obvious correctness.
★not rated 55
changed 3d agoA38 tokens
originalMIT
A testing-only workflow that turns a bug report into one test that should fail against the current code. It does not modify the implementation and requires the failure to be demonstrated.
Reviews Godot 4.7+ code or game-design changes against the repository's selected skills. Use after implementation or when the user asks for a focused review. Read-only.
Analyzes type design for encapsulation quality, invariant expression, usefulness, and enforcement, providing quantitative ratings and actionable improvement suggestions.
Start codebase analysis. Analyze single entity/action only. Return detailed analysis, recommendations, implementation guidance, usage examples. Prefer dependencylibraries-related-files-search first. Provide all relevant context (files, paths, symbols, imports, etc.). One topic or one context per request → wait for the…
Git history specialist — surgical commits with honest messages, history inspection (log/diff/blame/reflog), and when/why/who questions answered from evidence.
Research current external information, official library/API documentation, and comparisons. Verify claims against primary sources and return findings with source URLs and limitations.
★not rated 2 2d agoA32 tokens
originalMIT
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: