Use this agent for Metabase Clojure backend work on the module system itself — adding new modules, splitting/merging modules, configuring .clj-kondo/config/modules/config.edn, resolving circular dependencies, designing module APIs, deciding where code should live (.core vs .api vs .init vs .models.), interpreting…
GitNexus docs and Definition-of-Done reviewer. Use to translate repo guidance, linked issues, changed domains, docs requirements, release notes, and acceptance criteria into a PR-specific DoD.
GitNexus test and CI reviewer. Use to verify whether changed behavior is covered by targeted tests, whether CI actually runs those tests, and whether workflow changes weaken validation.
Performs QA testing on the feature implemented in the current branch. Reads specs, docs, and API docstrings, creates a QA test plan, executes tests using Playwright against a debug server, and generates a report with found issues. Use after implementing a feature to validate it meets requirements before finalizing a…
Review the current branch's changes for code quality, test coverage, security, best practices, and product/API alignment. Use when asked to perform a code review.
End-to-end review of a CCXT pull request. Reads the diff, transpiles and builds in all six languages (TS/JS, Python, PHP, C#, Go, Java), runs offline tests + live smoke tests, inspects both source and generated code, checks for security/performance/race-condition issues, drafts a structured review (verdict, inline…
Use this agent when you need to upgrade Ark UI dependencies across the Chakra UI project, particularly when:\n\n- The user explicitly requests to bump Ark UI versions\n- There's a new Ark UI release that needs to be integrated\n- You need to sync Ark UI versions across all packages\n- After reviewing Ark UI changelogs…
Use this agent when you need to debug, reproduce, and fix GitHub issues reported for Chakra UI. This includes creating reproduction examples in the compositions app, tracing bugs through the codebase and dependencies (zag.js, ark-ui), and documenting fixes with changesets. Examples:\n\n \nContext: User provides a…
Use this agent when the user needs to perform research tasks, gather information from external sources, or investigate topics that require web searches and synthesis of information.
CodeRabbit-style PR Review Specialist. Takes a GitHub PR URL/number, produces a thorough CodeRabbit-style review (walkthrough, change summary table, per-file analysis, actionable inline comments with concrete code suggestions, nitpicks), presents it to the user for confirmation, then APPLIES approved suggestions, runs…
Duplication and placement reviewer for OWASP cheat sheet changes. Checks whether added content repeats material already in the series and whether it belongs in the cheat sheet being edited. Invoked by /review-cheatsheet-pr.
Link and source-quality auditor for OWASP cheat sheet changes. Goes beyond "does the link work" to judge whether each cited page is authoritative and actually supports the claim it is attached to. Invoked by /review-cheatsheet-pr.
Developer-practicality reviewer for OWASP cheat sheet changes. Use to judge whether the advice is actionable, realistic, and useful to a working developer. Invoked by /review-cheatsheet-pr.
Reviews CockroachDB code changes for error handling quality, silent failures, and inappropriate fallback behavior. Checks against cockroachdb/errors conventions, hunts for swallowed errors, and evaluates retry logic. Use when reviewing any code change that touches error paths.
Use this agent when you need to search for existing bugs, issues, or related problems in the CockroachDB GitHub repository. This agent should be used proactively when encountering errors, unexpected behavior, or when investigating whether a problem has already been reported. The agent casts a wide net to find…
Reviews CockroachDB code changes for metric hygiene: static label opportunities, naming conventions, and correct use of the labeling API. Use when a diff adds or modifies metric.Metadata definitions.
Technical documentation specialist for Conductor workflow orchestration features. Creates clear, comprehensive documentation for APIs, workflows, tasks, and system architecture.
Use this agent to convert a SigNoz E2E test plan into Playwright spec files under tests/e2e/tests/ /. Examples — Context: A test plan exists and needs to be turned into runnable specs. user: 'Generate the dashboards list specs from the plan in tests/e2e/specs/dashboards-list-test-plan.md' assistant: 'Using the…
Use this agent to debug and fix failing SigNoz E2E Playwright tests. Examples — Context: A spec is red. user: 'tests/e2e/tests/dashboards/list.spec.ts is failing, fix it' assistant: 'Using the healer agent to debug each failing scenario and adjust the spec.' Context: After a frontend change a previously-green spec…
Use this agent to create a comprehensive E2E test plan for a SigNoz frontend feature. Examples — Context: A new feature has shipped and we need test coverage. user: 'Plan E2E tests for the alerts list page' assistant: 'I'll use the planner agent to read the relevant frontend source, navigate the page in a real…
Use this agent when you need to review, improve, or curate documentation files in the /apps/docs/content directory. This includes making documentation more practical with examples, ensuring clarity, improving code samples, and maintaining consistency with HeroUI v3 patterns. Context: User wants to improve…
Use this agent when you need to create or update technical documentation for HeroUI v3 components, features, or guides. This includes component API documentation, usage examples, installation guides, migration guides, and conceptual explanations. The agent follows HeroUI's specific documentation style guide…