skills.rest
erazemk
erazemkCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

git-commit

Validate staged git changes and draft DevRev-compliant commit messages.

Updated Jun 7, 2025
Search Tags:#automation#git#workflow#commit#guidance#version-control#devrev
One-click install
npx skills add https://github.com/erazemk/dotfiles --skill git-commit-erazemk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/erazemk/dotfiles/tree/main/agents/skills/git-commit
Command: npx skills add https://github.com/erazemk/dotfiles --skill git-commit-erazemk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This solution helps developers create git commits that follow DevRev conventions by guiding the user through inspecting changes, staging only appropriate files, and drafting a standards-compliant message.

Core Features & Use Cases

  • Staging guidance: avoids committing sensitive files by filtering what is staged.
  • Commit message drafting: generates a message that follows the DevRev format and includes the necessary issue ID.
  • Approval workflow: presents the full commit message and requires user approval before executing the commit.
  • Use Case: when preparing a feature or bugfix, ensure the commit adheres to DevRev conventions and includes the issue reference.

Quick Start

Provide a DevRev-compliant commit for your changes by entering an issue ID and confirming the final message.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I write a git commit message that follows DevRev conventions?▼

To write a DevRev-compliant git commit message, you provide an issue ID and the Skill drafts a message matching the required format based on your staged changes. It presents the full message and awaits your approval before executing the commit.

How does this git commit workflow handle sensitive files during staging?▼

The git commit workflow handles sensitive files by filtering what gets staged, providing staging guidance to avoid committing them. It inspects your changes and ensures only appropriate files are included before drafting the commit message.

Can I use this commit drafting tool if I have unstaged or missing changes?▼

Yes, you can use this commit drafting tool with unstaged or missing changes. It handles typical development workflows by inspecting the current state, guiding you to stage appropriate files, and then drafting the commit message.

What is the required format for a DevRev-compliant commit message?▼

A DevRev-compliant commit message requires a format that includes a necessary issue ID. The Skill enforces this format automatically when generating the draft from your staged changes.

Do I need to provide an issue ID before drafting a DevRev commit?▼

Yes, you need to provide an issue ID before drafting a DevRev commit. The Skill requires this ID to generate a standards-compliant message that properly references the issue in the commit.

Related Skills

Explore More Software Engineering Skills→
kristofferrembackkristofferremback
2

commit

Create conventional git commit messages from staged changes with Linear ticket IDs.

Community
Basic
AndrewDrygaAndrewDryga
28

release

Create semantic version tags from changelogs and push them to Git.

Community
Advanced
CrazyDubyaCrazyDubya

git-workflow-enforcer

Enforce Conventional Commits, branch naming, and PR templates via Git hooks.

Community
Advanced
mvillmowmvillmow
18

generate-changelog

Generate a Markdown changelog from git commits grouped by conventional commit types.

Community
Basic