rs-review

Append advisory UI observations to review-status.json using curated screenshots.

Updated Nov 7, 2025
One-click install
npx skills add https://github.com/rootspec/rootspec --skill rs-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rs-review
Source: https://github.com/rootspec/rootspec/tree/main/skills/rs-review
Command: npx skills add https://github.com/rootspec/rootspec --skill rs-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide an advisory visual assessment of the rendered UI using a small curated screenshot set. This advisory stage runs AFTER static review has already written authoritative findings and does not overwrite them.

Core Features & Use Cases

  • After a static review has produced authoritative findings, generate advisory observations about UI rendering, accessibility, and visual consistency using a curated screenshot set.
  • Reads and respects rootspec/review-status.json, and only writes to the llmFindings key.
  • Uses the curated screenshots listed in llmInputs.screenshots to surface human-like observations for review decisions.

Quick Start

Run rs-review after static review to append advisory findings to review-status.json using the curated screenshot set.

Frequently Asked Questions about rs-review

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

FAQPage Schema
How do I get advisory visual feedback on UI screenshots after a static review?

An advisory UI review appends human-like visual observations to the llmFindings key in review-status.json without overwriting the authoritative static findings already recorded.

Can I run an advisory UI review without overwriting existing static findings?

Yes, the advisory UI review runs after static review and only writes to the llmFindings key, leaving existing authoritative static findings in review-status.json completely unaltered.

When do I need an AI-assisted visual review for accessibility and UI consistency?

An AI-assisted visual review is needed when you want to surface advisory observations about UI rendering, accessibility, and visual consistency using curated screenshots after static analysis is complete.

How to add visual observations to review-status.json using curated screenshots?

Add visual observations by running an advisory review that reads the curated screenshots defined in llmInputs.screenshots and appends its visual findings exclusively to the llmFindings key in review-status.json.

Does advisory visual review work with existing review workflows?

Yes, advisory visual review works in review workflows where an existing review-status.json holds authoritative findings and llmInputs.screenshots define the curated visuals for generating advisory observations.

What is the best way to review rendered UI visuals without altering static test results?

The best way to review rendered UI visuals without altering static test results is to run an advisory review that references seed and philosophy documents for context while writing only to the llmFindings key.