review-community-standard-componentization-tests-knowledge

Name: review-community-standard-componentization-tests-knowledge
Availability: InStock
Author: Theo

Assess RED tests against diffs for test pyramid balance and formatting.

Updated May 13, 2026

Search Tags:#tdd #edge-cases #fixtures #bdd #given-when-then #aaa #tests-review

Ready to run

npx skills add https://github.com/usetheodev/theo-ui --skill review-community-standard-componentization-tests-knowledge

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review-community-standard-componentization-tests-knowledge
Source: https://github.com/usetheodev/theo-ui/tree/main/.claude/skills/review-community-standard-componentization-tests-knowledge
Command: npx skills add https://github.com/usetheodev/theo-ui --skill review-community-standard-componentization-tests-knowledge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tests-review knowledge skill for coordinating with review-community-standard-componentization-tests agent. Helps ensure test pyramids, AAA/Given-When-Then formats, fixture quality, and edge-case coverage are applied to plan reviews.

Core Features & Use Cases

Knowledge anchors for test pyramid balance, AAA/Given-When-Then patterns, and fixture quality.
Plan-aware evaluation of RED tests vs code diffs to identify gaps and opportunities.
Web-search-backed canonical practices to guide decisions and reduce ambiguity.

Quick Start

Review the plan against the current diff and pull canonical TDD/BDD practices from the web to guide your assessment.

Frequently Asked Questions about review-community-standard-componentization-tests-knowledge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I review TDD test quality against a code diff?▼

Reviewing TDD test quality involves comparing RED tests against the code diff to identify coverage gaps, then assessing test pyramid balance, AAA formatting, and fixture quality to ensure alignment with planned changes.

What is the best way to check edge-case coverage and fixture quality in BDD tests?▼

Checking edge-case coverage and fixture quality involves evaluating Given-When-Then patterns and mock discipline, using plan-aware evaluation against code diffs to identify missing edge cases and opportunities to improve fixture reliability.

How do I assess test pyramid balance for componentization plans?▼

Assessing test pyramid balance involves evaluating the distribution of unit, integration, and end-to-end tests within the plan, comparing RED tests against code diffs and applying canonical best practices sourced via web research to guide decisions.

Do I need web search to validate current TDD and BDD best practices during a review?▼

Web search is needed to validate current TDD and BDD best practices during a review, sourcing canonical guidance via web research during evaluation to reduce ambiguity and ensure decisions align with up-to-date industry standards.

Does AAA formatting matter when reviewing tests for componentization?▼

AAA formatting matters when reviewing tests for componentization because it enforces clear Arrange-Act-Assert separation, and evaluating AAA alongside Given-When-Then patterns ensures test readability and adherence to structured BDD practices.