skills.rest
AKMofficial
AKMofficialCOMMUNITY
Explore all skills by this author →
𝕏@AbdulkarimAJanGitHub

verify

Compare outputs and UI renders to verify unstaged edits preserve functionality.

1|1|Updated Mar 20, 2026
Search Tags:#safety#verify#code-review#code-cleanup#git-diff#unstaged#regression-check
One-click install
npx skills add https://github.com/AKMofficial/CC-Setup --skill verify-akmofficial
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/AKMofficial/CC-Setup/tree/main/skills/verify
Command: npx skills add https://github.com/AKMofficial/CC-Setup --skill verify-akmofficial

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unstaged edits can introduce bugs or alter behavior or UI; this skill helps ensure code cleanup or edits do not change final output or user experience.

Core Features & Use Cases

  • Compare outputs and UI to ensure parity across changes.
  • Validate that code modifications preserve behavior and appearance.
  • Use case: before staging changes, confirm no unintended side effects across components.

Quick Start

Run the verify workflow to confirm that unstaged changes preserve behavior and appearance.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I verify unstaged changes are safe before staging?▼

To verify unstaged changes are safe, compare outputs, UI renders, and interaction behavior before and after the edits to confirm final functionality and appearance remain consistent.

What is the best way to check code cleanup for unintended side effects?▼

Checking code cleanup for unintended side effects requires evaluating whether modifications preserve behavior and appearance by comparing outputs and UI parity across the altered components.

Can I use a regression check to validate refactoring without altering the UI?▼

A regression check can validate refactoring without altering the UI by comparing UI renders and interaction behavior to confirm the changes preserve the original user experience.

When do I need to run a git diff analysis for code review?▼

You need to run a git diff analysis for code review during code cleanup, refactoring, or ad hoc edits to determine if the modifications are safe and necessary to stage.

Does evaluating unstaged edits work across different components in a codebase?▼

Evaluating unstaged edits works across different components in a codebase by confirming no unintended side effects across components through output and UI parity validation.

Why does code refactoring sometimes alter UI consistency unexpectedly?▼

Code refactoring alters UI consistency unexpectedly when modifications change final output or user experience, requiring an evaluation of UI renders to confirm parity before staging.

Related Skills

Explore More Software Engineering Skills→
theslashdojotheslashdojo

git-diff

Identify and review exact changes across git states with unified diff output.

Official
Advanced
changoo89changoo89
19

code-cleanup

Remove dead code and unused imports from TypeScript and JavaScript codebases.

Community
Advanced
clinecline
65.9k

tuistory

Automate terminal UI interaction and testing in headless environments.

Official
Advanced
aniruddh2003aniruddh2003
1

speckit.checker

Run static analysis tools to detect security vulnerabilities, type errors, and linting issues.

Community
Intermediate