commit

Automates pre-commit validation checks including tests, static analysis, and conventional commit enforcement.

41|6|Updated Jul 12, 2025
One-click install
npx skills add https://github.com/SteveGJones/ai-first-sdlc-practices --skill commit-stevegjones
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/SteveGJones/ai-first-sdlc-practices/tree/main/plugins/sdlc-core/skills/commit
Command: npx skills add https://github.com/SteveGJones/ai-first-sdlc-practices --skill commit-stevegjones

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures you don't commit broken code by running quick validations before commit.

Core Features & Use Cases

  • Pre-commit validation: Run quick checks (tests, imports, lint-like steps) before committing.
  • Safe commits: Stop the commit if validations fail, guiding you to fix issues first.
  • Conventional commits: Suggests or enforces conventional commit formatting for traceability.

Quick Start

Run the commit workflow to validate changes and commit only if checks pass.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I run pre-commit validation checks before committing code?

Pre-commit validation checks run quick tests, static analysis, and import checks before allowing a git commit. The process stops the commit if validations fail, guiding you to fix issues first.

How do I enforce conventional commit messages in my local development workflow?

Enforcing conventional commit messages during local development ensures traceability by suggesting or requiring specific formatting before a commit is allowed. This prevents improperly formatted messages from being submitted.

Can I stop a git commit if my tests fail locally?

You can stop a git commit if tests fail locally by running pre-commit validation. When tests are configured, the validation process blocks the commit and guides you to resolve the failing tests first.

What is the best way to ensure code quality before committing changes?

The best way to ensure code quality before committing changes is automating pre-commit validation. This runs configured tests and static analysis checks, blocking the commit if any code quality checks fail.

Do I need a specific testing framework to run pre-commit checks?

No specific testing framework is required, but pre-commit checks run tests when they are configured in your local development environment. The validation ensures that whatever tests are set up pass before committing.