commit

Stage changes, validate builds and tests, then commit with formatted messages and issue references.

Updated Jan 25, 2026
One-click install
npx skills add https://github.com/Pjpj42/GridRacer --skill commit-pjpj42
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/Pjpj42/GridRacer/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/Pjpj42/GridRacer --skill commit-pjpj42

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automate the governance of code changes by validating builds and standardizing commit messages, reducing broken CI runs and tangled history.

Core Features & Use Cases

  • Build verification: Validate changes before committing to ensure the code builds and tests pass.
  • Change awareness: Review what will be committed with git status and diff.
  • Issue integration: Encourage or enforce references to issues in commit messages and offer guidance when missing.
  • Structured commits: Stage and commit with a descriptive message, optionally including Co-Authored-By metadata.

Quick Start

Stage your changes, ensure the build passes, and commit with a descriptive message.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I validate my build and tests before making a git commit?

To validate your build before a git commit, this Skill stages your changes and automatically runs build and test verification, ensuring the code passes checks before finalizing the commit message and preventing broken CI runs.

What's the best way to enforce issue references in git commit messages?

To enforce issue references in commit messages, this Skill validates your staged changes and provides guidance when issue references are missing, ensuring structured commits that integrate properly with your software development workflow and code review processes.

How does automated change awareness work when preparing staged files for a commit?

Automated change awareness reviews what will be committed by analyzing git status and diff outputs, ensuring you have full visibility of staged changes before the build verification and commit message generation steps occur.

Can I include Co-Authored-By metadata in standardized commit messages?

Yes, you can include Co-Authored-By metadata in commit messages. This Skill stages and commits changes with a descriptive, structured message, optionally appending the Co-Authored-By trailer to maintain proper attribution in your git history.

Why do my continuous integration runs keep failing after unverified git commits?

Continuous integration runs often fail from unverified git commits due to broken builds or failing tests. This Skill solves this by validating builds and standardizing commit messages before submission, reducing tangled history and CI failures.