verify-then-commit

Enforces tests, typecheck, and linting before committing via pre-commit hooks.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/thomas-estep/bindle --skill verify-then-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-then-commit
Source: https://github.com/thomas-estep/bindle/tree/main/skills/verify-then-commit
Command: npx skills add https://github.com/thomas-estep/bindle --skill verify-then-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that code is of high quality by enforcing mandatory checks before commits, reducing the risk of deploying broken code.

Core Features & Use Cases

  • Mandatory Checks: Enforces running tests, typecheck, and lint before committing.
  • Pre-commit Hook: Integrates with pre-commit hooks to enforce these checks.
  • Use Case: Before pushing code to a repository, this Skill ensures that all tests pass, typechecking is successful, and linters have no issues.

Quick Start

Before committing changes, run the verify-then-commit command to ensure all checks pass.

Frequently Asked Questions about verify-then-commit

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

FAQPage Schema
How do I enforce code quality checks before committing changes?

To enforce code quality checks before committing, you can use pre-commit hooks integrated with code linters to prevent broken code from being deployed to your repository.

What is the best way to run tests and typecheck before a git commit?

The best way to run tests and typecheck before a git commit is by enforcing mandatory checks through a pre-commit hook, ensuring all validations pass successfully before code is committed.

Can I use pre-commit hooks to block commits if linting fails?

Yes, pre-commit hooks can block commits if linting fails, enforcing mandatory code quality checks to ensure linters have no issues before allowing changes to be committed to the repository.

Do I need code linters to enforce mandatory commit checks?

Yes, code linters are required to enforce mandatory commit checks, working alongside pre-commit hooks to verify that tests pass, typechecking succeeds, and code quality is maintained.

Why should I run code verification before pushing to a repository?

Running code verification before pushing to a repository reduces the risk of deploying broken code by ensuring all tests pass, typechecking is successful, and linters have no issues.

What are the limitations of using pre-commit hooks for code verification?

Pre-commit hooks for code verification rely on the local development environment, meaning they can be bypassed by developers and do not replace the need for server-side repository checks.