skills.rest
luigiinred
luigiinredCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

dev-workflow-validate-change

Analyze git diffs and capture screenshots of affected app screens via Maestro.

1|Updated Feb 18, 2026
Search Tags:#automation#code review#screenshots#visual testing#git diff#maestro
One-click install
npx skills add https://github.com/luigiinred/dotfiles --skill dev-workflow-validate-change
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-workflow-validate-change
Source: https://github.com/luigiinred/dotfiles/tree/main/dot_cursor/skills/dev-workflow-validate-change
Command: npx skills add https://github.com/luigiinred/dotfiles --skill dev-workflow-validate-change

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the visual validation of code changes by capturing screenshots of affected application screens on a device, ensuring that new code integrates correctly and doesn't introduce visual regressions.

Core Features & Use Cases

  • Automated Screenshot Capture: Captures screenshots of specific application screens based on code changes.
  • Visual Regression Testing: Helps identify unintended visual side effects of code modifications.
  • Use Case: After pushing a change to a UI component, use this skill to automatically generate screenshots of all screens that use that component, allowing for a quick visual review before merging.

Quick Start

Use the dev-workflow-validate-change skill to validate your current code changes by taking screenshots of affected screens.

Frequently Asked Questions about dev-workflow-validate-change

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

FAQPage Schema
How do I visually validate code changes before merging?▼

To visually validate code changes, this Skill analyzes git diffs to identify affected application screens and captures screenshots via Maestro. It delegates device interaction to automatically generate visual output of your code modifications.

How do I capture screenshots of app screens affected by a git diff?▼

Capturing screenshots of app screens affected by a git diff is done by analyzing the code changes and automatically taking screenshots via Maestro. The Skill delegates to maestro-take-screenshots to interact with the device and capture the visual output.

Can I automate visual regression testing using git diffs?▼

Yes, you can automate visual regression testing using git diffs. The Skill identifies unintended visual side effects of code modifications by analyzing the diffs and capturing screenshots of the specific application screens that use the modified components.

Do I need Maestro to automatically screenshot UI changes?▼

You need Maestro to automatically screenshot UI changes because this Skill delegates to maestro-take-screenshots and maestro-explore for device interaction. These skills handle the actual capture of application screens based on the analyzed git diff.

What is the best way to see visual output of modified UI components?▼

The best way to see visual output of modified UI components is to use this Skill to analyze your git diff and capture screenshots of all screens that use that component. This allows for a quick visual review before merging your code.

Related Skills

Explore More Software Engineering Skills→
maxmurrmaxmurr

generating-commit-messages

Generate commit messages from git diff --staged with WHAT/WHY summaries.

Community
Basic
EvolutionAPIEvolutionAPI
520

dev-visual-verdict

Compare before and after screenshots to detect visual regressions in UI components.

Official
Intermediate
luigiinredluigiinred
1

maestro-take-screenshots

Capture screenshots and video recordings of mobile app pages using Maestro.

Community
Intermediate
nateanatea

visual-testing-advanced

Detect and quantify visual regressions across web UI screenshots.

Community
Advanced