verifying-changes

Validate code changes through linting, browser testing, and console monitoring.

Updated Aug 23, 2026

Search Tags:#code quality #testing #bug fixing #verification #chrome mcp #ui changes

Ready to run

npx skills add https://github.com/anthony-fdez/claude-skills --skill verifying-changes

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verifying-changes
Source: https://github.com/anthony-fdez/claude-skills/tree/main/.claude/skills/verifying-changes
Command: npx skills add https://github.com/anthony-fdez/claude-skills --skill verifying-changes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that code changes are thoroughly validated through automated checks and manual verification, preventing bugs and regressions before deployment.

Core Features & Use Cases

Automated Quality Checks: Runs linters and formatters to catch code style and type errors.
Browser Verification: Uses Chrome MCP to visually inspect UI changes and test user interactions.
Use Case: After implementing a new feature with UI modifications, use this Skill to first run npm run formatAndLint, then verify the visual output and interactivity in the browser using Chrome MCP, and finally check the console and network for any silent errors.

Quick Start

Run the verifying-changes skill to check the latest code modifications.

Frequently Asked Questions about verifying-changes

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

FAQPage Schema

How do I verify code changes and prevent regressions after modifying UI?▼

Browser-based verification using Chrome MCP visually inspects UI changes, tests user interactions like form submissions, and monitors console and network activity to detect silent errors that automated linters miss.

How do I test API endpoints and forms for functional correctness in the browser?▼

You can test API endpoints and forms for functional correctness by using Chrome MCP to interact with the UI and monitor network requests, ensuring the endpoints respond correctly without silent errors.

Can I use Chrome MCP to check console and network errors after code changes?▼

Yes, Chrome MCP supports checking console and network errors after code changes by performing interactive browser testing that monitors both console logs and network activity to catch silent runtime issues.

What's the best way to run automated code quality checks before browser verification?▼

The best way to run automated code quality checks before browser verification is to execute linting and formatting commands, such as npm run formatAndLint, to catch code style and type errors first.

Does this verification process require any specific dependencies or environment setup?▼

This verification process requires Chrome MCP for browser-based UI verification and interactive testing, but has no other listed dependencies, allowing it to run within a standard development environment.