review-and-qa

Analyze code changes to generate a structured QA review plan.

60|40|Updated May 19, 2025
One-click install
npx skills add https://github.com/storyblok/monoblok --skill review-and-qa
Or copy as Structured Prompt for Agentβ–Ό
Please help me install this Agent Skill.
Skill: review-and-qa
Source: https://github.com/storyblok/monoblok/tree/main/.claude/skills/review-and-qa
Command: npx skills add https://github.com/storyblok/monoblok --skill review-and-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill analyzes code changes (commit, branch, or pull request) to produce a structured QA review plan.

Core Features & Use Cases

  • Two-phase review: Code review for quality and architecture, and QA review to generate manual test cases and a test plan.
  • Output artifacts: Generates a markdown QA plan with prioritized test scenarios and a reusable checklist.
  • Use Case: When a PR is opened, run this skill to automatically draft a QA workflow and test cases for the changes.

Quick Start

Use the review-and-qa skill to generate a QA plan for a PR or commit.

Frequently Asked Questions about review-and-qa

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

FAQPage Schema
How do I generate a QA test plan from a pull request?β–Ό

To generate a QA test plan from a pull request, analyze the code changes to produce a structured review document. This process outputs a ready-to-use markdown plan with prioritized test scenarios, acceptance criteria, and reusable checklists for manual testing.

What is included in a code review and QA workflow for a new branch?β–Ό

A code review and QA workflow for a new branch includes a two-phase process: evaluating code quality and architecture, followed by QA review. It generates manual test cases, structured checklists, and actionable test scenarios to validate the commit changes.

Can I automatically draft manual test cases when a PR is opened?β–Ό

Yes, you can automatically draft manual test cases when a PR is opened by analyzing the code changes. This generates a structured QA plan document containing prioritized test scenarios and reusable checklists to guide manual testing efforts immediately.

What's the best way to create acceptance criteria for code changes in a commit?β–Ό

The best way to create acceptance criteria for code changes in a commit is to run a structured QA review. This analyzes the modifications and outputs a markdown document featuring defined acceptance criteria, test scenarios, and checklists to verify quality.

Do I need any dependencies to produce a structured QA review plan?β–Ό

No dependencies are required to produce a structured QA review plan. The skill operates standalone to analyze your branch or pull request changes and output a markdown document with checklists and manual test cases without needing external components.