skills.rest
sizukutamago
sizukutamagoCOMMUNITY
Explore all skills by this author →
GitHub

verified-commit

Run lint, type-check, and tests before commits.

Updated Feb 4, 2026
Search Tags:#workflow#commit#pre-commit#lint#ci#tests#type-check
One-click install
npx skills add https://github.com/sizukutamago/dev-tools-plugin --skill verified-commit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verified-commit
Source: https://github.com/sizukutamago/dev-tools-plugin/tree/main/skills/verified-commit
Command: npx skills add https://github.com/sizukutamago/dev-tools-plugin --skill verified-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates pre-commit verification to ensure code quality by running lint, type checking, and tests before commits.

Core Features & Use Cases

  • Quick verification: runs lint and type checks to provide fast feedback before committing.
  • Full verification: runs lint, type checks, and tests for critical changes.
  • Flexible workflow: adapts to TypeScript, JavaScript, shell, and Python projects using common tools (tsc, ESLint, Biome, and npm test).

Quick Start

Make changes and trigger the verification workflow:

  • Quick mode (default): run tsc --noEmit, then lint (npx eslint) to validate changes before commit.
  • Full mode: run the quick checks plus tests (npm test).

Frequently Asked Questions about verified-commit

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

FAQPage Schema
How do I run lint and type-check validation before committing code?▼

To run lint and type-check validation before committing, this skill automates quick verification by executing tsc --noEmit and lint tools like ESLint or Biome to provide fast feedback on your changes.

What is the best way to automate pre-commit checks for TypeScript and Python projects?▼

Automating pre-commit checks for multi-language projects is done by adapting to your local tooling, running tsc, ESLint, and npm test to ensure code quality before changes are committed.

Do I need to configure ESLint or Biome locally to use pre-commit verification?▼

Yes, you need project-local tooling configured in your repository, such as tsc, ESLint or Biome, and npm test, because the verification skill executes these existing commands directly.

Can I run tests alongside lint and type-checks before a git commit?▼

Yes, you can run tests alongside lint and type-checks by using full verification mode, which executes npm test in addition to the quick mode lint and type-check validations for critical changes.

When should I use quick mode versus full mode for pre-commit verification?▼

Use quick mode for fast feedback by running only lint and type-checks, and use full mode for critical changes where you need lint, type-checks, and tests executed before committing.

Related Skills

Explore More Software Engineering Skills→
tejovanthntejovanthn
1

biome-tooling

Configure Biome formatting and linting for JavaScript/TypeScript projects.

Community
Intermediate
Room-CRoom-C

rc:commit

Stage, format, and push git changes with conventional commits.

Official
Intermediate
gautam-achieveaigautam-achieveai
2

clean-builds

Automates code quality tools and package version validation in .NET projects.

Community
Advanced
yashs33244yashs33244
1

setup-pre-commit

Set up Husky pre-commit hooks with lint-staged and Prettier for Node.js repositories.

Community
Intermediate