skills.rest
OpenSourcePharmaFoundation
OpenSourcePharmaFoundationCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

commit

Generate a Conventional Commits message from the current Git staged diff.

4|1|Updated Jan 8, 2024
Search Tags:#git#version control#conventional commits#monorepo#commit message#staged changes
One-click install
npx skills add https://github.com/OpenSourcePharmaFoundation/ospf-ayurveda-kg --skill commit-opensourcepharmafoundation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/OpenSourcePharmaFoundation/ospf-ayurveda-kg/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/OpenSourcePharmaFoundation/ospf-ayurveda-kg --skill commit-opensourcepharmafoundation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you avoid vague, inconsistent commit messages by turning your staged changes into a clear Conventional Commits message.

Core Features & Use Cases

  • Conventional Commits formatting: Produces messages with standard types like feat, fix, docs, chore, refactor, and test to keep your Git history readable.
  • Staged-changes only: Analyzes only what you have staged, preventing accidental references to unrelated work.
  • Monorepo-aware tagging: Uses package abbreviations in parentheses when changes affect specific packages, keeping commit metadata consistent across the repo.

Quick Start

Use the commit skill to write a Conventional Commit message for the changes currently staged in Git.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I generate a conventional commit message from staged changes?▼

To generate a conventional commit message from staged changes, analyze your Git staged diff using git status and git diff to produce a concise message reflecting change intent and package scope.

How does monorepo-aware tagging work for conventional commits?▼

Monorepo-aware tagging for conventional commits uses package abbreviations in parentheses when changes affect specific packages, ensuring commit metadata remains consistent across the repository.

Can I use conventional commits to only analyze staged files and ignore unstaged work?▼

Yes, the conventional commit generation process reads only staged files via git status and git diff, preventing accidental references to unrelated or unstaged work in your repository.

What are the allowed commit types for conventional commits in a monorepo?▼

Allowed conventional commit types include standard categories like feat, fix, docs, chore, refactor, and test, keeping your Git history readable and structured across monorepo packages.

Why does my conventional commit message not reflect the correct package scope?▼

Your conventional commit message might lack correct package scope if changes affect multiple packages or if monorepo abbreviation rules are not properly applied to the staged diff.

What is the best way to maintain consistency in Git commit messages across a monorepo?▼

The best way to maintain consistency in Git commit messages across a monorepo is to apply conventional commits formatting with monorepo-aware tagging that uses package abbreviations for specific staged changes.

Related Skills

Explore More Software Engineering Skills→
az9713az9713

git-commit

Stage changes with git add and commit using Conventional Commits format.

Community
Intermediate
ctrsploitctrsploit
153

commit-message

Generate semantic Git commit messages from staged changes using Conventional Commits.

Official
Intermediate
mgoodman60mgoodman60

commit

Generate descriptive Git commit messages from repository changes with conventional formatting.

Community
Basic
791994545791994545
4

git-commit

Analyze git diffs to generate conventional commit messages and stage files.

Community
Intermediate