commit

Validate, stage, and commit code changes with conventional commit messages.

Updated Feb 13, 2026
One-click install
npx skills add https://github.com/g-zenr/relay-api --skill commit-g-zenr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/g-zenr/relay-api/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/g-zenr/relay-api --skill commit-g-zenr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of creating clean, validated, and consistently formatted Git commits, ensuring code quality and maintainability.

Core Features & Use Cases

  • Pre-commit Validation: Ensures tests and type checks pass before committing.
  • Guided Staging: Helps you selectively stage only relevant files, avoiding accidental commits of sensitive data or build artifacts.
  • Conventional Commit Generation: Enforces a standardized commit message format for better project history.
  • Use Case: Before committing a new feature, this Skill will guide you through verifying your code, staging only the necessary files, and crafting a commit message like feat(api): add new user endpoint.

Quick Start

Use the commit skill to create a conventional commit for your current changes.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I create conventional commits in Git without manually formatting the message?▼

To generate conventional commits, this skill validates your changes, guides selective file staging, and formats a standardized message like feat(api): add endpoint to maintain project history.

How can I prevent accidental commits of build artifacts or sensitive data in Git?▼

To prevent accidental commits, this skill provides guided staging to help you selectively stage relevant files, ensuring build artifacts and sensitive data are excluded from version control.

Can I enforce pre-commit checks for tests and type checks before committing code?▼

Yes, you can enforce pre-commit checks. This skill ensures tests and type checks pass before committing, directly enforcing code quality and maintainability standards.

What is the conventional commit format and when should I use specific commit types and scopes?▼

The conventional commit format structures messages with specific types and scopes, such as feat or fix. Use this format to create a clean, validated, and consistently structured project history.

What is the best way to selectively stage files for a Git commit?▼

The best way to selectively stage files is using guided staging. This skill helps you stage only relevant modified files, preventing accidental commits while enforcing pre-commit validation checks.