verify

Name: verify
Availability: InStock
Author: donygeorge

Verify code changes with automated checks and inline summaries.

2|Updated Feb 16, 2026

Search Tags:#automation #edge-cases #code #verify #lint #changes #tests

Ready to run

npx skills add https://github.com/donygeorge/claude-toolkit --skill verify-donygeorge

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/donygeorge/claude-toolkit/tree/main/skills/verify
Command: npx skills add https://github.com/donygeorge/claude-toolkit --skill verify-donygeorge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifies code changes after implementation to ensure correctness, helping teams catch regressions and validate outcomes before merging.

Core Features & Use Cases

Runs automated checks after code changes to confirm tests, lint, and style constraints.
Scans edge cases, identifies unexpected behaviors, and surfaces actionable fixes.
Produces an inline summary instead of creating external report files, and prompts for input when clarification is needed.
Supports deep verification and quick checks across uncommitted changes, commit ranges, or plan-based scopes, integrated with other skill invocations like /implement or /fix.

Quick Start

Run /verify to start thorough verification of your latest changes and view an inline summary.

Frequently Asked Questions about verify

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

FAQPage Schema

How do I verify code changes after implementing a feature or bug fix?▼

Verify code changes by running automated checks across uncommitted changes or commit ranges to confirm tests, lint, and style constraints, scanning edge cases, and surfacing actionable fixes inline.

What is the best way to check for regressions and edge cases before merging code?▼

Check for regressions by running a deep verification process that scans edge cases, identifies unexpected behaviors, automatically fixes unambiguous issues, and prompts for user input when clarification is needed.

Can I run a quick check on just my uncommitted changes?▼

Yes, you can run a quick check on uncommitted changes to validate correctness rapidly, supporting both deep verification and quick checks across various scopes including plan-based scopes.

Does verification support checking a specific commit range?▼

Yes, verification supports checking specific commit ranges, allowing you to validate outcomes and ensure correctness across defined commit boundaries or plan-based scopes.

How does verification handle ambiguous code issues it finds?▼

When verification encounters ambiguous issues, it asks for user input to clarify, while automatically fixing only unambiguous problems and returning an inline summary without external report artifacts.