commit

Stage, review, type-check, and format Git commits with conventional messages.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents messy or risky Git commits by guiding you through staging, diff review, type checking, and conventional-commit formatting before creating the commit.

Core Features & Use Cases

  • Staged diff review before committing: verifies exactly what will be recorded and flags likely issues like leftover debug code or unintended changes.
  • Meetily KPI risk scanning (advisory): compares the staged changes against the repo’s core KPI set and warns when a KPI might regress.
  • Pre-commit type checking: runs cargo check for Rust and/or pnpm tsc --noEmit for TypeScript as appropriate, blocking commits on failures.
  • Conventional commit enforcement: creates a Conventional Commits message with a short summary (and optional body) and avoids disallowed trailers.
  • No push behavior: ensures the skill never pushes to remote, keeping commit creation separated from release workflows.

Quick Start

Run commit changes and message in one step by telling the assistant: "commit this with message 'feat: add commit safety checks'."

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate conventional commits with type checking for Rust and TypeScript?

You can automate conventional commits by staging specific files, reviewing the diff, and running mandatory type checks like cargo check or pnpm tsc --noEmit to block risky commits. This ensures clean, safe commit messages without pushing.

What is a conventional commit and how does a pre-commit safety check work?

A conventional commit formats Git changes using types like feat, fix, or refactor. Pre-commit safety checks review staged diffs and run type checks to block commits if errors or unintended debug code are detected.

Can I use git add -A to stage all files before generating a conventional commit message?

No, you cannot use git add -A or git add . because explicit staging of specific files is required. This prevents unintended changes from being included in your conventional commit.

Does this workflow automation tool push commits to the remote repository?

No, the workflow automation strictly separates commit creation from release workflows and never pushes to the remote repository. It only performs local staging, diff review, type checking, and commit formatting.

How do I run cargo check and pnpm tsc --noEmit on staged content before committing?

Pre-commit verification automatically runs cargo check for Rust and pnpm tsc --noEmit for TypeScript on your staged content. If these type checks fail, the commit process is blocked to ensure code safety.

Why does my commit get blocked during diff review?

Your commit gets blocked during diff review if mandatory type checks like cargo check or pnpm tsc --noEmit fail, or if the review flags likely issues such as leftover debug code or unintended changes.