skills.rest
michaelvolz
michaelvolzCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

rm-commit

Create repo-specific conventional commit payloads from the working tree.

Updated Nov 11, 2023
Search Tags:#git#staging#conventional-commits#commit workflow#repo rules#here-string
One-click install
npx skills add https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb --skill rm-commit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rm-commit
Source: https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb/tree/main/.opencode/skills/rm-commit
Command: npx skills add https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb --skill rm-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill keeps git commits clean and reviewable by guiding you through repo-specific staging, formatting, and conventional messaging without pushing or exposing secrets.

Core Features & Use Cases

  • Repository Rules First: Directs you to inspect AGENTS.md or CLAUDE.md before making any changes to respect project-specific constraints.
  • Commit Shaping Flow: Walks through status, diff, branch, history, and selective staging to form coherent, single-purpose commits.
  • Conventional Commit Messaging: Enforces padded body lines, specific footer references, and a here-string pipeline so that commitlint requirements are met.

Quick Start

Ask the assistant to run the rm-commit flow, stage the relevant hunks, and pipe a properly wrapped conventional commit message via the here-string command.

Frequently Asked Questions about rm-commit

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

FAQPage Schema
How do I create conventional commit messages from my git working tree?▼

Conventional commits are created by inspecting git status and diff, selectively staging hunks, and piping a structured message with padded body lines under 80 characters via a here-string command.

What's the best way to ensure my git commits respect repo-specific rules?▼

Repo-specific rules are enforced by checking AGENTS.md or CLAUDE.md before staging to respect project constraints, then shaping single-purpose commits through status, diff, branch, and history inspection.

How do I stage git changes safely without exposing secrets or pushing?▼

Safe staging is achieved by walking through git status and diff to selectively stage relevant hunks while forbidding git revert and push operations to prevent accidental exposure or history changes.

Does this conventional commit workflow support commitlint requirements?▼

Commitlint requirements are met by enforcing padded body lines, specific footer references, and a here-string pipeline so that commit payloads conform to conventional commit formatting rules.

Can I use git push or git revert when running this commit workflow?▼

Git push and git revert are explicitly forbidden within this commit workflow, which focuses solely on inspecting status, staging safely, and formatting conventional commit messages.

Why do my conventional commit body lines need to be under 80 characters?▼

Conventional commit body lines must be under 80 characters to meet commitlint formatting requirements, ensuring structured and reviewable commit messages that pass linting checks.

Related Skills

Explore More Software Engineering Skills→
devturcodevturco

commit

Create a single git commit with a conventional-commits message.

Community
Intermediate
theodrosyimertheodrosyimer

conventional-commit

Generate commitlint-compliant conventional commit messages from staged diffs.

Community
Intermediate
SunS1eep1ngSunS1eep1ng

git-push

Automate Git commit and push workflows for GitHub repositories using Conventional Commits.

Community
Advanced
engakhattabengakhattab

speckit-git-commit

Block automated Git commits and output manual git add and commit commands.

Community
Basic