Use this agent when implementation is complete and code needs to be verified before committing or creating a PR. Triggers on phrases like "run quality gates", "check code quality", "run qa", "verify my changes", "pre-commit checks", "qa check", "act as qa lead", or when tech-lead or another agent suggests quality…
Use this agent when you need to debug Electron application issues, particularly UI-related problems, component rendering issues, or when you need to bypass native dialogs for testing. This agent specializes in visual debugging through screenshots and color manipulation, and can programmatically control the app for…
Use this agent when you need to run, debug, or troubleshoot end-to-end Electron tests. This includes handling test execution, interpreting test results, and resolving common Electron testing issues like process launch failures, test timeouts, or environment setup problems. Examples:\n\n \nContext: The user is working…
Runs greptile review on the current branch and returns a compact summary of findings. Use instead of running greptile review in the main session — its output quotes code blocks and inflates the main context.
Execute an already-reviewed phase.rs implementation plan surgically. Receives the approved plan + scope, edits files, runs Tilt-first verification, and returns a diff summary with any judgement-call notes. Does NOT plan, does NOT review, does NOT commit. Spawned by the /engine-implementer skill.
Reviews completed project steps against plans and enforces coding standards. Use when a numbered step from a plan is complete, a major feature is implemented, or before creating a PR. Validates plan alignment, code quality, test coverage, and architecture. Blocks merges for Minor, Important, or Critical issues.
Fixes issues identified by code-reviewer and triggers re-review. Use when code-reviewer returns any issues that need to be addressed before merge approval.
Implements individual tasks from plans with TDD, skill application, verification, and git commits. Use when executing a specific task that requires writing, modifying, or testing code as part of a larger plan.
Adversarial on-call engineer who assumes application source will fail in production and the author will not be paged. Audits application source, not infrastructure, for code-level resilience anti-patterns: missing timeouts, retries without backoff and jitter, non-idempotent operations in retry paths, catch-and-swallow…
Personal-repo curation agent. Sweeps this personal repo's scratch-lifecycle namespaces and proposes which ones to promote, merge, or archive. Lighter than the canon variant: this curator works on a single repo.
A subagent that retrieves relevant knowledge nodes by reading the local git tree, supplements with a web search, and produces a structured research summary with citations and suggested follow-up nodes.
Spec-review agent for empirical economics. Checks clustering level, FE absorption, weights, IV first-stage strength, multiple-hypothesis correction, sample selection, DiD assumptions, and SE method choice. Use on any analysis do-file before merging to main.
Use when a bundle-plugin needs systematic quality audit and security scan against the 10-category checklist. Dispatched by auditing for thorough automated assessment.
Audit all cli-web- CLIs for convention drift against skills/shared/CONVENTIONS.md, including replskin drift via cli-web-devkit drift and .manifest.json presence. Reports PASS/FAIL per check per CLI in a matrix format. Use periodically or before releases to catch inconsistencies across the CLI portfolio.
Use this agent when you need to prepare, validate, and publish a production release for a software project. This agent is designed for release engineering tasks including: preparing a new version release (e.g., 'Cut release v0.2.0 or v0.2.0-rc.1'), validating release readiness across all dimensions (code, packages…