How do I install the Commit skill?

Run npx skillmds@latest add tomevault-io/commit-51 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Commit safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Commit?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Commit free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Commit?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Commit by tomevault-io — Agent Skill

Name: Commit
Author: tomevault-io

File contents

Conventional Commit Generator

Create git commits following Conventional Commits specification.

Usage

Run /commit to analyze staged changes and create a properly formatted commit.

Workflow

Run git status and git diff --staged to see changes
Determine the commit type based on changes
Determine the scope (area of codebase)
Create commit with format: type(scope): description

Commit Types

feat - New feature (bumps minor version)
fix - Bug fix (bumps patch version)
docs - Documentation only
style - Code style changes
refactor - Code refactoring
perf - Performance improvement (bumps patch version)
test - Adding or fixing tests
build - Build system or dependencies
ci - CI configuration
chore - Other changes

Scopes for Fair-Forge

metrics - Metric implementations
runners - Test runners
generators - Data generators
storage - Storage backends
schemas - Pydantic models
core - Base classes
llm - LLM integration
guardians - Bias/toxicity guardians
deps - Dependencies

Commit Format

Simple: type(scope): description

Examples:

feat(metrics): add agentic evaluation metric
fix(toxicity): handle empty batches
docs: update installation guide
refactor(core): extract base retriever logic
test(runners): add integration tests
build(deps): upgrade langchain-core

For breaking changes, add exclamation mark after scope: feat(schemas)!: rename field

Rules

Use imperative mood: "add feature" not "added feature"
Keep description under 72 characters
Lowercase description
No period at end
NEVER add "Co-Authored-By" or any similar attribution line to commits

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: commit-51description: Create git commits following Conventional Commits format. Analyzes staged changes and generates properly formatted commit messages. Use when this capability is needed.---# Conventional Commit GeneratorCreate git commits following Conventional Commits specification.## UsageRun `/commit` to analyze staged changes and create a properly formatted commit.## Workflow1. Run `git status` and `git diff --staged` to see changes2. Determine the commit type based on changes3. Determine the scope (area of codebase)4. Create commit with format: `type(scope): description`## Commit Types- `feat` - New feature (bumps minor version)- `fix` - Bug fix (bumps patch version)- `docs` - Documentation only- `style` - Code style changes- `refactor` - Code refactoring- `perf` - Performance improvement (bumps patch version)- `test` - Adding or fixing tests- `build` - Build system or dependencies- `ci` - CI configuration- `chore` - Other changes## Scopes for Fair-Forge- `metrics` - Metric implementations- `runners` - Test runners- `generators` - Data generators- `storage` - Storage backends- `schemas` - Pydantic models- `core` - Base classes- `llm` - LLM integration- `guardians` - Bias/toxicity guardians- `deps` - Dependencies## Commit FormatSimple: `type(scope): description`Examples:- `feat(metrics): add agentic evaluation metric`- `fix(toxicity): handle empty batches`- `docs: update installation guide`- `refactor(core): extract base retriever logic`- `test(runners): add integration tests`- `build(deps): upgrade langchain-core`For breaking changes, add exclamation mark after scope: `feat(schemas)!: rename field`## Rules- Use imperative mood: "add feature" not "added feature"- Keep description under 72 characters- Lowercase description- No period at end- NEVER add "Co-Authored-By" or any similar attribution line to commits---> Converted and distributed by [TomeVault](https://tomevault.io/claim/alquimia-ai) — claim your Tome and manage your conversions.

Frequently asked questions

Commit