verification-first

Define verification plans and run automated checks before and after code implementation.

2|Updated May 15, 2026

Search Tags:#code quality #best practices #verification #software testing #development process

Ready to run

npx skills add https://github.com/bdbch/ai-dotfiles --skill verification-first-bdbch

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-first
Source: https://github.com/bdbch/ai-dotfiles/tree/main/skills/verification-first
Command: npx skills add https://github.com/bdbch/ai-dotfiles --skill verification-first-bdbch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill encourages a "Verify → Implement → Confirm" cycle, helping developers ensure their code works as intended before moving on.

Core Features & Use Cases

Verification-First Approach: Prioritize verification planning to catch issues early.
Automated Checks: Utilize unit tests, type checks, linters, and more for fast, repeatable verification.
Manual Verification: Define clear steps for manual checks when automation isn't possible.
Visual Verification: Specify what to look for in UI changes and other visual elements.
Regression Guard: Ensure existing functionality remains intact when implementing changes.
Use Case: Use before starting a new feature to define verification steps and after implementation to confirm functionality.

Quick Start

Before starting a task, create a verification plan for your code changes.

Frequently Asked Questions about verification-first

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

FAQPage Schema

What is a verification-first approach in software development?▼

A verification-first approach prioritizes planning code verification before implementation. It uses a structured cycle to define success criteria and test cases early, ensuring software correctness through unit testing, integration testing, and manual checks.

How do I define verification steps before starting a new feature?▼

To define verification steps, establish clear success criteria and create a verification plan. Outline specific automated checks like unit tests and linters, plus manual verification steps, to catch issues early before you implement the feature.

Can I use this verification process for visual UI changes?▼

Yes, the verification process supports visual UI changes. It allows you to specify exact visual elements to look for during manual checks, ensuring that interface updates function and appear as intended alongside automated tests.

What's the best way to prevent regressions when implementing code changes?▼

The best way to prevent regressions is applying a Verify-Implement-Confirm cycle. By running automated unit tests and integration tests before and after changes, you ensure existing functionality remains intact and guard against software regressions.

Do I need automated tests to use a structured verification process?▼

No, automated tests are recommended for fast and repeatable verification, but you can rely on manual verification. You define clear manual steps for checks when automation is not possible, ensuring code correctness without mandatory automated testing.