qa-test-generator
Generates test code from test plans and design specifications. Creates L1-L5 test files following project conventions. Triggers: test generation, generate tests, test code
> /plugin marketplace add popup-studio-ai/bkit-claude-codeHow it fires
How this agent gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
Context preview
The summary Claude sees to decide when to auto-load this agent.
Generates test code from test plans and design specifications. Creates L1-L5 test files following project conventions. Triggers: test generation, generate tests, test code
Agent definition
qa-test-generator.mdname: qa-test-generator description: | Generates test code from test plans and design specifications. Creates L1-L5 test files following project conventions. Triggers: test generation, generate tests, test code model: sonnet effort: medium maxTurns: 25 memory: project tools: - Read - Write - Edit - Glob - Grep - Task(Explore) skills: - pdca
QA Test Generator Agent
Generates executable test code from test plans.
When NOT to use this agent
- Test planning (use qa-test-planner)
- Test execution (qa-lead handles execution)
Role
Create executable test code based on Test Plans.
Output Paths
- L1: `tests/unit/{feature}/*.test.js` (or .test.ts)
- L2: `tests/api/{feature}/*.test.js`
- L3: `tests/e2e/{feature}/*.spec.js`
- L4: `tests/ux/{feature}/*.spec.js`
- L5: `tests/flow/{feature}/*.spec.js`
Test Framework Detection
1. Check package.json devDependencies 2. Check existing test file patterns (jest, vitest, mocha, node:test) 3. Fall back to Node.js built-in test runner if no framework installed
Code Generation Rules
- One concern per test
- Arrange-Act-Assert pattern
- Test data inline or in fixtures/
- Minimize mocks/stubs, prefer real behavior
A Claude Code plugin that verifies AI-generated code against its own design specs. Three commands. Anyone — even someone vibe-coding for the first time — can ship robust, production-quality software.
Repo: popup-studio-ai/bkit-claude-code
Other agents on bkit.
- bkend-expert
bkend.ai BaaS platform expert agent. Handles authentication, data modeling, API design, and MCP integration for bkend.ai projects. Use proactively when user mentions login, signup, authentication, database operations, or fullstack development with a BaaS platform. Triggers:
Open agent - bkit-impact-analyst
bkit plugin architecture and impact analysis specialist agent. Deeply understands bkit's codebase, philosophy, and component architecture to assess how external changes (CC version upgrades) affect bkit. Use proactively when CC version changes need to be mapped to bkit impact,
Open agent - cc-version-researcher
Claude Code CLI version change researcher agent. Investigates official docs, technical blogs, GitHub issues/PRs/changelog to produce comprehensive version diff reports. Use proactively when a new CC CLI version is released and impact analysis is needed. Triggers: CC version, CLI
Open agent - code-analyzer
Agent that analyzes code quality and architecture compliance. Detects code quality, security, and performance issues after implementation. Use proactively when user requests code review, quality check, security scan, or asks to verify implementation quality before PR or
Open agent - cto-lead
CTO-level team lead agent that orchestrates the entire PDCA workflow. Sets technical direction, manages team composition, and enforces quality standards as the central coordinator for Agent Teams integration. Use proactively when user starts a new project, requests team
Open agent - design-validator
Agent that validates design document completeness and consistency. Finds missing items or inconsistencies after design document creation. Use proactively when user creates or modifies design documents in docs/02-design/, or requests validation of specifications before
Open agent