verify

Review code changes, test results, and project plans before deployment.

4|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/0xmariowu/builders-dont-cry --skill verify-0xmariowu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/0xmariowu/builders-dont-cry/tree/main/core/skills/verify
Command: npx skills add https://github.com/0xmariowu/builders-dont-cry --skill verify-0xmariowu

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides an independent review mechanism to validate finished work, ensuring safety and quality before deployment or release.

Core Features & Use Cases

  • Verification of Diff and Evidence: Examines code changes, test results, and verification reports to confirm correctness.
  • Scope Assessment: Checks for scope drift and scope boundaries based on project files and plans.
  • Use Case: When a team completes a feature, use this Skill to verify code diffs, plan compliance, and safety issues prior to shipping a release.

Quick Start

Invoke the verify skill after completing code review to perform an independent verification of the latest changes.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I automate code review and diff inspection before deployment?

Automated code review and diff inspection validates finished work by examining code changes, test results, and project plans. It performs independent verification using Bash, Task, Read, and Grep tools to confirm correctness and safety before shipping.

What is scope drift validation in software engineering?

Scope drift validation checks for scope boundaries and compliance based on project files and plans. It ensures completed features match intended boundaries, preventing unauthorized changes from reaching deployment during the verification process.

Can I use automated verification for test results and evidence inspection?

Automated verification examines test results and verification reports to confirm correctness. It inspects evidence within development workflows, ensuring code changes meet safety and quality standards before release.

When do I need independent review for code changes?

Independent review for code changes is needed when a team completes a feature and requires validation of code diffs, plan compliance, and safety issues. It ensures correctness prior to shipping a release.

Does automated verification work with Bash and Grep tools?

Automated verification uses specified tools like Bash, Task, Read, and Grep for verification purposes. These tools enable diff analysis, scope validation, and evidence inspection within development workflows.

What are the limitations of automated code verification before shipping?

Automated code verification focuses on diff analysis, scope validation, and evidence inspection. It provides an independent review mechanism but should be invoked after completing code review to perform final verification of latest changes.