verify

Automate pre-commit verification with build, test, and lint checks.

412|45|Updated Feb 19, 2026

Search Tags:#testing #quality assurance #code review #debugging #verification #pre-commit

Ready to run

npx skills add https://github.com/cwinvestments/memstack --skill verify-cwinvestments

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill prevents broken code from being committed by automating checks against requirements and common issues, saving time and reducing bugs.

Core Features & Use Cases

Automated Checks: Runs build, test, and lint commands relevant to the project.
Manual Requirement Check: Compares implemented work against original task requirements.
Common Issue Scan: Detects uncommitted debug code, hardcoded values, and missing error handling.
Use Case: Before pushing a new feature, you can ask the AI to "verify this work" to get a comprehensive report on its quality and adherence to requirements.

Quick Start

Use the verify skill to check the current work before committing.

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 checks before a git commit?▼

Pre-commit code review checks are automated by running build, test, and lint commands alongside a scan for debug remnants and manual requirement validation to ensure code quality before committing.

What is the best way to verify completed code against project requirements?▼

The best way to verify completed code is to compare implemented work against original task requirements while simultaneously running automated build, test, and lint checks to catch common development issues.

Can I use automated pre-commit checks if my project uses different frameworks?▼

Yes, automated pre-commit checks operate framework-agnostic by detecting project tooling automatically, allowing the verification process to run relevant build, test, and lint commands regardless of framework.

How do I scan for debug remnants and hardcoded values in my code?▼

Scanning for debug remnants and hardcoded values is handled by a common issue scan that detects uncommitted debug code, hardcoded values, and missing error handling during the verification process.

What common development issues should I check before pushing a new feature?▼

Before pushing a new feature, check for uncommitted debug code, hardcoded values, missing error handling, build failures, test failures, and linting errors to get a comprehensive quality report.

Does pre-commit verification work without configuring specific testing tools?▼

Pre-commit verification works without manual configuration because it detects project tooling automatically, running the relevant build, test, and lint commands that apply to your specific environment.