skills.rest
adamrdrew
adamrdrewCOMMUNITY
Explore all skills by this author →
GitHub

describe-review-file

Generate review documentation scaffolds with predefined sections for product, code, and QA reviews.

7|1|Updated Jan 27, 2026
Search Tags:#template#documentation#qa#scaffold#review#code-review
One-click install
npx skills add https://github.com/adamrdrew/ushabti --skill describe-review-file
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: describe-review-file
Source: https://github.com/adamrdrew/ushabti/tree/main/skills/describe-review-file
Command: npx skills add https://github.com/adamrdrew/ushabti --skill describe-review-file

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes and speeds up the creation of review documentation by providing a ready-made scaffold that defines essential sections and structure.

Core Features & Use Cases

  • Predefined sections: Summary, Verified, Issues, Required follow-ups, and Decision to ensure consistent reviews.
  • Template-driven workflow: Applies to product reviews, code reviews, and QA assessments to capture findings and actions in a uniform format.
  • Scaffold reuse: Quickly generate new review documents for ongoing workflows and new features.

Quick Start

Create a new review.md using this scaffold to standardize your review workflow.

Frequently Asked Questions about describe-review-file

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

FAQPage Schema
How do I create a standardized review document for code reviews and QA findings?▼

A review document scaffold provides a ready-made template with predefined sections such as Summary, Verified, Issues, Required follow-ups, and Decision to standardize product, code, and QA review documentation.

What sections should be included in a QA findings or code review template?▼

A QA findings or code review template should include Summary, Verified, Issues, Required follow-ups, and Decision sections to capture findings, actions, and final outcomes in a uniform format.

What is the best way to standardize unstructured review documentation across multiple workflows?▼

The best way to standardize unstructured review documentation is applying a reusable scaffold that enforces consistent sections, allowing you to quickly generate new review documents for ongoing workflows and new features.

Can I use a review scaffold for both product reviews and code reviews?▼

Yes, you can use a review scaffold for both product reviews and code reviews because the template-driven workflow applies to any assessment requiring uniform capture of findings, actions, and decisions.

Do I need any specific dependencies or components to generate a review document scaffold?▼

No dependencies or components are required to generate a review document scaffold, as the template is self-contained and defined by the frontmatter name and description in its SKILL.md file.

Related Skills

Explore More Content & Communication Skills→
MiniMax-AIMiniMax-AI
2.9k

skill-creator

Generate Skill Units with YAML frontmatter, Markdown body, and bundled resources.

Official
Intermediate
dev-goraebapdev-goraebap

draft-public-rules

Draft a track-aware public rules document choosing between AGENTS.md and CLAUDE.md for your project.

Community
Advanced
fauzanazzfauzanazz

feature-docs

Generate markdown feature documentation with templates and context extraction.

Community
Advanced
peteromalletpeteromallet
97

dogfood

Automate exploratory QA testing of web applications with evidence-based bug reports.

Community
Advanced