review

Runs full backend, frontend, and e2e test suites and outputs PR readiness recommendations.

Updated Aug 30, 2025
One-click install
npx skills add https://github.com/ajmartin94/CookingAssistant --skill review-ajmartin94
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/ajmartin94/CookingAssistant/tree/main/.claude/skills/review
Command: npx skills add https://github.com/ajmartin94/CookingAssistant --skill review-ajmartin94

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Final gate before PR. Runs the full test suite to catch regressions, then reviews code against the plan and project standards. Use this skill when: (1) TDD is complete and the branch needs validation before PR, (2) the user says "review" or "ready for PR", (3) multiple TDD runs have completed and the branch needs a final check.

Core Features & Use Cases

  • Orchestrates cross-layer test runs (backend, frontend, and end-to-end) to verify branch health.
  • Collects failures, categorizes them, and presents guided options for resolution (update tests, fix failures, or revert).
  • Validates code against the plan and standards, and facilitates decision-making for PR readiness.

Quick Start

Validate the branch after TDD completion by running the full review to ensure PR readiness.

Frequently Asked Questions about review

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

FAQPage Schema
How do I validate a branch for PR readiness after TDD is complete?

To validate PR readiness after TDD, run an end-to-end review that executes the full test suite across backend, frontend, and e2e layers. It surfaces failures and validates code against the plan, providing structured recommendations for your next steps.

What does automated code review check before merging a pull request?

Automated code review checks for regressions by running cross-layer tests and validates the code against project standards and plan artifacts. It categorizes test failures and presents guided options for resolution before the PR is merged.

Can I use this review skill if my TDD cycle is not finished yet?

No, this review skill applies specifically to branches where TDD is complete and a PR is pending. Using it earlier means the full test suite and code validation will run against incomplete test coverage, failing to accurately gate PR readiness.

How do I handle test failures discovered during pre-PR validation?

When pre-PR validation discovers test failures, the review process categorizes them and guides you to decide on the appropriate resolution. You can choose to update tests, fix the failures, or revert based on plan conformance.

What is the best way to run end-to-end tests before creating a pull request?

The best way to run end-to-end tests before a PR is to automate the orchestration of backend, frontend, and e2e test layers. This collects all failures in one pass, ensuring branch health and facilitating final PR readiness decisions.

Do I need plan artifacts to run an automated code review?

Yes, plan artifacts are required to run this automated code review. The skill requires access to plan artifacts and test results to validate whether the code conforms to the original plan and project standards.