skills.rest
instrument-org
instrument-orgOFFICIAL
Explore all skills by this author →
Website𝕏@tryinstrumentGitHub

find-ui-changes

Identify user interface changes from commit history for review.

3|Updated Apr 6, 2026
Search Tags:#code review#commit analysis#design verification#UI change detection#Instrument
One-click install
npx skills add https://github.com/instrument-org/instrument --skill find-ui-changes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: find-ui-changes
Source: https://github.com/instrument-org/instrument/tree/main/.agents/skills/find-ui-changes
Command: npx skills add https://github.com/instrument-org/instrument --skill find-ui-changes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the identification of UI changes made by Instrument commits, simplifying the process of review and handoff for designers and developers.

Core Features & Use Cases

  • UI Change Detection: Identifies changes in user interfaces based on commit data.
  • Review Queue Creation: Generates a concise queue of review-worthy UI changes for designers.
  • Use Case: After a code merge, quickly create a list of UI changes that require human review to ensure quality and consistency.

Quick Start

Use the find-ui-changes skill to find recent UI changes for the last 2 weeks.

Frequently Asked Questions about find-ui-changes

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

FAQPage Schema
How do I automate UI change detection from commit history?▼

Automating UI change detection involves parsing commit subjects and file changes to identify modified user interface surfaces, generating a concise review queue for subsequent design verification.

What is the best way to create a design review queue for post-merge code changes?▼

Creating a design review queue for post-merge code changes involves analyzing recent commit data to isolate user interface modifications, producing a targeted list of review-worthy UI surfaces for designers to verify quality and consistency.

How does automated UI change identification work for design verification workflows?▼

Automated UI change identification for design verification works by evaluating commit data to isolate user interface modifications, then extracting relevant file changes to produce a queue of surfaces requiring human review.

Can I identify UI changes in my application commits from the last 2 weeks?▼

Yes, you can identify UI changes in application commits from the last 2 weeks by analyzing the commit history to isolate user interface modifications and generating a concise review queue for design verification.

Does UI change detection require specific dependencies to run post-merge code review?▼

No specific dependencies are required to run post-merge code review for UI change detection, as the skill operates using included scripts to parse commit data and identify user interface modifications independently.

When should I use automated UI change identification versus manual code review?▼

You should use automated UI change identification when processing post-merge commits to quickly isolate user interface modifications, saving manual code review effort for evaluating the generated queue of review-worthy UI surfaces.

Related Skills

Explore More Design & Creative Skills→
weisser-devweisser-dev
22

changelog-generate

Generate CHANGELOG.md from git history using Keep a Changelog format.

Community
Intermediate
jesserathbunjesserathbun

build-feature

Orchestrate end-to-end feature development with a single approval gate in Atlas.

Community
Advanced
openkaidenopenkaiden
3

coderabbit-review

Fetch and triage CodeRabbitAI review comments from GitHub pull requests.

Official
Intermediate
kazdenckazdenc
42

quieter

Desaturate colors, soften contrast, and simplify visual elements in UI designs.

Community
Intermediate