Builds exactly one weft node end to end, unsupervised. Dispatched by Tangle with a typed contract (one job, exact ports); researches the real API documentation when the node wraps a service, writes the node and extensive tests in the project's nodes/ folder, and proves it by running weft test-node on the local tiers…
Orchestrates full feature implementation across models, controllers, views, and tests following 37signals conventions. WHEN: Implementing a full feature end-to-end, coordinating multi-layer changes, building new CRUD resources. WHEN NOT: Reviewing existing code (use review-agent), refactoring legacy patterns (use…
Writes tests for existing behaviour. Adds and edits test files only — never touches production code. Use for coverage backfill where the bulk of the work is mechanical.
Investigate Flutter test failures to determine root causes and whether issues are in code or tests. Use PROACTIVELY when flutter tests fail or need debugging. Expert in Riverpod, widget testing, and VGE patterns.
An independent code-review and testing role for Java projects. It writes tests from the project rules before implementation, then checks the finished code against those rules across seven review areas.
You are a test-writing specialist for the harness-kit monorepo. You receive a function, module, or feature to test and produce high-quality tests that follow this project's conventions exactly.
Use this agent when tests need to be written, debugged, or improved. For example: writing XCTest unit tests for a view model, creating XCUITest UI tests for a user flow, setting up mock services for testing, debugging a flaky test, increasing test coverage, writing snapshot tests, or configuring a test plan.
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.
Generates and hardens the test suite — unit AND end-to-end — for a change, runs it, and validates the behavior actually works (not just that assertions pass). Use as the SAFETY GATE before any autonomous fix is approved or merged: no adequate tests, no green light. The thing that makes the autonomous loops safe.
Writes tests and runs verification for a Ralph user story that has already been implemented by ralph-coder. Creates unit/integration/e2e tests, runs story verification commands, and runs the full regression suite. Used by ralph-orchestrator as the second phase of story execution.
Review test code for resource cleanup, mock hygiene, and best practices in Bun/Node.js projects. Use after writing tests or when debugging flaky tests.
Writes tests for existing behaviour. Adds and edits test files only — never touches production code. Use for coverage backfill where the bulk of the work is mechanical.
Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.
Writes unit and integration tests for new or modified code. Use this agent when the user asks to add test coverage, test-drive a feature, or when a PR lacks tests.
Senior QA and ML/LLM Test Engineer specialized in test strategy, test writing, coverage analysis, regression tests, data and feature contracts, ML pipeline validation, and LLM/agent/RAG evaluation. Use for designing test suites, writing tests for existing code, building bug-reproduction tests, evaluating coverage, or…
★not rated 2 4mo agoA82 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: