verify

Verify completed work with automated build, test, and lint checks before committing.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/jtucker9/mystuff --skill verify-jtucker9
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/jtucker9/mystuff/tree/main/skills/verify
Command: npx skills add https://github.com/jtucker9/mystuff --skill verify-jtucker9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifies that completed work meets defined requirements before committing, reducing regressions and manual follow-ups.

Core Features & Use Cases

  • Automated checks: builds, tests, and lint runs to ensure code quality before commit.
  • Manual verification: a structured requirement review to capture edge cases and acceptance criteria.
  • Guardrails: provides a repeatable protocol to detect common issues and prevent unsafe changes in your workflow.

Quick Start

Run the verification protocol on your latest changes before committing to ensure all checks pass.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I run automated checks before committing code changes?

To verify code changes before committing, run an automated protocol that executes builds, tests, and lint checks to ensure code quality. This process detects common issues and prevents unsafe changes from reaching your main workflow.

What is a pre-commit verification protocol for software engineering?

A pre-commit verification protocol is a structured process that combines automated build, test, and lint runs with a manual requirement review. It ensures completed work meets defined requirements and captures edge cases before pushing commits.

Can I use automated checks alongside a manual requirement review?

Yes, you can verify work using both automated checks and a manual requirement review. The protocol applies structured automated builds and test runs, then follows with a manual review to capture edge cases and acceptance criteria.

What's the best way to prevent regressions before pushing commits?

The best way to prevent regressions is to verify completed work against defined requirements before committing. Applying a repeatable protocol with automated checks and manual reviews reduces regressions and manual follow-ups.

Does pre-commit verification work without external dependencies?

Yes, pre-commit verification works without external dependencies. The protocol operates independently to apply automated build, test, and lint checks, followed by a final verification report for your code changes.