skills.rest
akirschke15-cmd
akirschke15-cmdCOMMUNITY
Explore all skills by this author →
GitHub

commit

Validate TypeScript types and tests before creating a conventional commit.

Updated Mar 28, 2026
Search Tags:#code quality#git#typescript#unit testing#conventional commits#release hygiene#ci readiness
One-click install
npx skills add https://github.com/akirschke15-cmd/Cato-Registry --skill commit-akirschke15-cmd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/akirschke15-cmd/Cato-Registry/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/akirschke15-cmd/Cato-Registry --skill commit-akirschke15-cmd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents broken builds and inconsistent history by enforcing a repeatable commit workflow that includes type checking, test verification, and a consistent conventional commit message format.

Core Features & Use Cases

  • Type safety gate: Runs TypeScript type checking to ensure no type errors are introduced before committing.
  • Regression confirmation: Executes the test suite and validates that tests pass (or no tests exist) to avoid shipping regressions.
  • Audit-friendly commit hygiene: Promotes clear diffs and standardized messages so teams can understand changes quickly and maintain a searchable history.
  • Use Case: After finishing an API feature or UI refactor, use this Skill to verify correctness, summarize changes by area, and create a conventional commit that documents intent.

Quick Start

Run the commit workflow to verify types and tests, review your diffs, then create and push a conventional commit for the current branch, reporting the resulting commit hash.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate TypeScript type checking and unit tests before a Git commit?▼

To automate TypeScript type checking and unit tests before a Git commit, you can run a workflow that executes tsc --noEmit and npm test, ensuring code correctness before staging changes and creating a conventional commit.

What is the best way to format conventional commit messages for CI readiness?▼

The best way to format conventional commit messages for CI readiness is to use the <type>(<scope>) structure, keeping the message under 72 characters to document intent and maintain a searchable, audit-friendly Git history.

How does running tsc --noEmit prevent broken builds during TypeScript development?▼

Running tsc --noEmit prevents broken builds by acting as a type safety gate that catches TypeScript type errors before changes are staged and committed, ensuring no type regressions are introduced into the codebase.

Can I run npm test with passWithNoTests when verifying code before committing?▼

Yes, you can run npm test with passWithNoTests handling when verifying code before committing, allowing the workflow to validate test suites and pass successfully even if no tests exist for the current changes.

Does this commit workflow handle pushing changes and returning the commit hash?▼

Yes, this commit workflow handles pushing changes to the remote repository and returning the resulting commit hash, completing the process of staging, committing, and pushing your verified code changes.

Related Skills

Explore More Software Engineering Skills→
a2musa2mus

speckit-verify

Automate codebase verification across builds, type checks, linting, tests, and git status.

Community
Intermediate
pythoninthegrassespythoninthegrasses
1

changelog-automation

Generate changelogs and release notes from commits, PRs, and tags.

Official
Advanced
phuonghxphuonghx
1

lint-and-validate

Automate linting, formatting, type checking, and security audits for Node.js/TypeScript and Python codebases.

Community
Advanced
shellicarshellicar

git-workflow

Validate Git commit messages, staging practices, and push commands.

Community
Intermediate