Choose a testing workflow that fits the repository’s behavior, fixtures, framework, and non-negotiable test commands.
The job
Includedregression tests · feature behavior tests · adapting to repository test conventions
Not this pagebrowser automation platform setup · load testing · security testing
30-second route
It has the strongest task fit and the best public-recognition rank among the broad, source-supported options (303), while explicitly preserving the project’s actual runner.
Editorial confidence: highIt directly covers adding tests to legacy React components and provides concrete provider, async, network-mocking, accessibility, and test-layer guidance.
Editorial confidence: highIts behavior and regression guidance is directly useful, but its commands and repository-specific rules must be adapted.
Editorial confidence: mediumIts source says not to look at existing code and to delete code written before the test, which seriously conflicts with adding coverage to an already implemented feature.
Editorial confidence: highBefore you install
No new skill is needed. The strict TDD finalist is excluded for a concrete mismatch with testing already implemented behavior, while the selected skills retain explicit, usable test-authoring guidance.
Read the intervention guide →Source-led comparison
Facts are extracted from each selected Skill’s declared workflow. Signals describe public adoption; they are not a universal score.
Source notes
Why these candidatesEach candidate comes from tracked public sources and has a source-attributed adoption signal. This is a shortlist, not a catalogue or global ranking.
What this cannot establishWe read declared instructions and public signals. We do not run skills, benchmark outputs, audit security, or claim a universal best choice.
Use it forA general existing-feature test task where the repository’s package manager and actual test runner must be discovered first.
Avoid ifYou need a narrowly framework-specific workflow, such as React-only test utilities.
ActionInstall and use its runner-discovery step before adding focused behavior or regression coverage.
EditsInspect the repository test script and nearby tests; add behavior, error, and boundary cases using the established runner.
SetupResolve the package manager and distinguish it from the test runner before choosing commands.
ContextBroad JavaScript/TypeScript-oriented TDD workflow with unit, integration, and optional E2E patterns.
OutputFocused tests plus an appropriate test and coverage command.
ControlStructured workflow with explicit runner detection and RED/GREEN verification.
InvocationNot yet mapped from the source.
Install scopeNot yet mapped from the source.
Agent fitStrong general-purpose choice; it avoids assuming npm and distinguishes Bun’s native runner from a package script.
Watch outIts 80% coverage target and optional E2E material are guidance, not a reason to introduce browser automation for this task.
The skill activates for bug fixes and refactoring, and requires tests before implementation.SKILL.md:L10-L24 · inspected 2026-07-20 · high confidence
It directs the user to inspect the repository’s actual test script and test files rather than assume npm test.SKILL.md:L51-L77 · inspected 2026-07-20 · high confidence
It distinguishes behavior-focused assertions from implementation-detail tests and includes error and boundary coverage expectations.SKILL.md:L371-L417 · inspected 2026-07-20 · high confidence
Use it forExisting React components, hooks, or pages that need regression or behavior coverage.
Avoid ifThe feature is not React, or the repository does not use React Testing Library-compatible component tests.
ActionInstall when the feature is React; follow nearby tests and choose RTL, component testing, or E2E at the documented boundary.
EditsAdd accessible, user-driven assertions; use provider wrappers and MSW only where the feature needs them.
SetupUse the repository’s existing Vitest or Jest setup; render with the production-equivalent providers where applicable.
ContextReact-specific test-authoring guide for RTL, Vitest/Jest, MSW, accessibility, hooks, and escalation to browser tests.
OutputA focused component, hook, or page test that checks observable behavior.
ControlBehavior-first with clear framework and test-layer decision boundaries.
InvocationNot yet mapped from the source.
Install scopeNot yet mapped from the source.
Agent fitBest specialist option for React code; more actionable than a generic TDD guide for providers, async UI, and network mocks.
Watch outDo not introduce Playwright or Cypress unless the feature needs real-browser behavior that JSDOM cannot cover.
It is intended for writing tests for React components, hooks, pages, and legacy untested components.SKILL.md:L10-L20 · inspected 2026-07-20 · high confidence
It requires production-equivalent providers, accessible interactions, and observable assertions rather than implementation-detail checks.SKILL.md:L22-L36 · inspected 2026-07-20 · high confidence
It gives an explicit decision boundary between RTL, real-browser component testing, and full E2E.SKILL.md:L264-L280 · inspected 2026-07-20 · high confidence
Use it forA Vitest-based feature or bug-fix test task where focused execution, behavior assertions, and boundary-level mocks are desired.
Avoid ifThe repository is not Vitest-based or its test commands and conventions cannot be safely adapted from this LobeHub-oriented guide.
ActionAdapt its focused-test and regression-test practices to the repository’s own commands and test layout.
EditsWrite a regression test that fails before the fix when applicable; test observable output or side effects and mock only external boundaries.
SetupReplace its LobeHub-specific Bun/Vitest commands and package paths with the repository’s documented commands.
ContextVitest guide with targeted commands, behavior-testing principles, regression expectations, and mock guidance.
OutputA focused Vitest spec, then the affected suite and relevant type check.
ControlPractical repository workflow that favors integration-level behavior over white-box checks.
InvocationNot yet mapped from the source.
Install scopeNot yet mapped from the source.
Agent fitUseful Vitest substitute when the existing project already has a fast, focused test path.
Watch outThe supplied commands and database conventions are LobeHub-specific; do not copy them unchanged into another repository.
The skill explicitly applies to writing or updating tests, improving coverage, and setting up mocks.SKILL.md:L1-L5 · inspected 2026-07-20 · high confidence
It directs bug fixes to add a regression test and says to test behavior rather than implementation details.SKILL.md:L40-L48 · inspected 2026-07-20 · high confidence
It recommends integration-level observable assertions and mocks at database, network, and external-service boundaries.SKILL.md:L111-L122 · inspected 2026-07-20 · high confidence
Still comparing?