Ralph Tester — Development agent for Claude Code
Writes tests and runs verification for a Ralph user story that has already been implemented by ralph-coder.
How to install Ralph Tester
Installs to ~/.claude/agents/cfircoo-claude-code-toolkit-ralph-tester.md
mkdir -p ~/.claude/agents && curl -fsSL https://raw.githubusercontent.com/cfircoo/claude-code-toolkit/HEAD/agents/ralph-tester.md -o ~/.claude/agents/cfircoo-claude-code-toolkit-ralph-tester.md Restart Claude Code, or start a new session, for it to be picked up.
What Ralph Tester does
name: ralph-tester description: 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. tools: Read, Bash, Write, Edit, Grep, Glob model: opus
You are Ralph's tester agent. Your job is to write tests and verify ONE user story that was already implemented by aAlternatives in Development
- Revert — Revert changes by logical work unit with full git awareness 31.9k ★
- Atlas — You are a specialized E2E testing agent 3.6k ★
- E2e Tester 427 ★
Full documentation available on GitHub
View Source RepositoryRelated Agents
Ralph Coder
Implements code for a single Ralph user story. Writes production code and documentation only — does NOT write
Gauntlet Coder
Builds one story to a written Gherkin specification — unit tests plus the implementation that satisfies them —
Integration Tester
Specializes in end-to-end integration testing, validating that frontend and backend work together correctly. U
Tool Author
Tool scaffolding expert for actual-mcp-server. Invoke when adding a new MCP tool end-to-end — file creation, r
E2e Author
Use to create or update end-to-end tests for user-facing flows changed by a story, using the repo's existing e
Flutter Tester
Use after any feature implementation, bug fix, or refactor. Writes and runs unit tests, bloc_tests, and widget
Related Skills
Architect Verify Traceability
Integration verification — confirm the issue → design → code → tests chain is intact, E2E + smoke suite pass,
Apply Proposal
Implement an APPROVED proposal — planner (if needed) -> coder (self-verify) -> reviewer; tester only if you as
Bead Sweep
Scan open beads for stale trackers already implemented — deterministic checks then LLM verification.