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.
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 for tasks involving compiler configuration in .properties files - adding, removing, modifying, or aliasing compilers. This includes understanding group structures, compiler properties, and maintaining shortlink compatibility when deprecating compilers. USE PROACTIVELY when the user mentions a PR adding…
Use this agent when you need expert guidance on Compiler Explorer architecture, design decisions, infrastructure considerations, or when planning changes that affect the core functionality or deployment of CE. This includes understanding the multi-repository structure, balancing needs between godbolt.org and local…
SCOPE: GENERAL CODE REVIEW (Primarily Go) This agent handles code review for both Go and Astro code, with focus on general software quality principles. Preferred Usage: ✅ Dingo transpiler/language (Go code in /cmd/, /pkg/, /internal/) ⚠️ Astro landing page (can review, but astro-reviewer is preferred for…
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…
SCOPE: ASTRO LANDING PAGE REVIEW ONLY This agent is EXCLUSIVELY for reviewing the Dingo landing page (Astro, React, TypeScript in /langingpage/ directory). ❌ DO NOT USE for: Dingo transpiler/language code review (use code-reviewer instead) Go code review in /cmd/, /pkg/, /internal/ (use code-reviewer instead) Parser…
Use this agent when you need expert guidance on Go development best practices, including code implementation, refactoring for idiomatic Go, performance optimization, error handling patterns, concurrency design, and architectural decisions. This agent excels at writing production-ready Go code that follows community…
Use this agent when you need expert review of Go code for best practices, idioms, performance, and correctness. This includes reviewing functions, packages, tests, or any Go code changes for adherence to Go conventions, error handling patterns, concurrency safety, and overall code quality. Examples:\n\n \nContext: The…
Use this agent when you need to create comprehensive test suites, write unit tests, integration tests, or test cases for existing code. This agent specializes in analyzing code to identify test scenarios, edge cases, and validation requirements, then implementing appropriate test coverage. Examples:\n\n \nContext: The…
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker (GitHub Issues — see issue-tracker.md).
Station AI agent operator. Use proactively for ANY Station-related tasks including creating agents, running tasks, managing environments, configuring MCP servers, deploying, and debugging agent workflows. Has full access to Station's 55+ MCP tools.
Station agents are intelligent AI assistants that can execute tasks using MCP (Model Context Protocol) tools. This guide covers creating, configuring, and deploying agents.
Station's environment system provides secure isolation for agents and tools across development, staging, and production environments. Each environment maintains its own MCP server pool, agent definitions, and configuration variables.
Keeps README.md and everything under docs/ in sync with the code, CLI, and config as they change. MUST BE USED before opening or updating a pull request, and any time behavior, flags, config schema, commands, or public API have changed. Reconciles docs against the actual change set and fixes drift.
Use this agent when the user wants to analyze the communication mechanism between the Flutter client and backend server, evaluate potential plugins/dependencies, and get architectural recommendations for improving robustness. This includes scenarios like:\n- \n Context: The user wants a comprehensive analysis of the…
Use this agent when the user wants to simulate Flutter client network requests against the backend using Python test scripts. This includes scenarios like testing button clicks, sending messages, navigating screens, or any user interaction that triggers backend API/WebSocket calls. The agent first reads Flutter code…