How do I install the Git Commit skill?

Run npx skillmds@latest add tomevault-io/git-commit-14 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 Git 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 Git 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 Git Commit free to use?

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

Who published Git Commit?

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

Git Commit by tomevault-io — Agent Skill

Name: Git Commit
Author: tomevault-io

Git Commit

Create clean, reviewable commits for TroubleScout by staging logically, writing emoji-prefixed messages, and following repo safety rules (no secrets, no force-push, no bypassing hooks). Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Git Commit (TroubleScout)

Use this skill when you need to turn working changes into one or more high-signal commits.

Inputs to gather

What was the intent of the change? (bug fix vs behavior change vs docs vs build/packaging)
Which areas are touched? (CLI entry, Copilot session behavior, PowerShell execution/safety, UI output, tools)
Is anything sensitive present in diffs? (tokens, hostnames, IPs, event log contents, stack traces with secrets)

Workflow

Confirm you are not on main.
Review the working tree (git status -sb) and inspect the diff (git diff).
Split unrelated changes into separate commits.
Stage intentionally:
- Prefer git add -p for mixed files.
- Avoid staging generated build output (bin/, obj/) unless explicitly requested.
If .cs files changed, run dotnet build before committing.
Write an emoji-prefixed commit subject line:
- Format: <emoji> <summary>
- Keep it short and specific; use imperative mood.
Commit without bypassing hooks (do not use --no-verify).

Emoji prefixes

Commit subjects must start with an emoji. Use any emoji; these are common conventions:

✨ New behavior / feature
🐛 Bug fix
♻️ Refactor
📝 Docs
🔧 Build/config
✅ Tests
🔖 Release/tagging

Message examples

✨ Add WinRM connectivity check
🐛 Fix null handling in Copilot delta events
🔧 Update publish defaults for win-x64
📝 Clarify release packaging instructions

Safety checks

Do not commit secrets (tokens, credentials), personal data, or sensitive server data.
If logs are required, redact/trim to the minimal necessary context.
Never force-push. Never rewrite published history.

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

---name: git-commit-14description: Create clean, reviewable commits for TroubleScout by staging logically, writing emoji-prefixed messages, and following repo safety rules (no secrets, no force-push, no bypassing hooks). Use when this capability is needed.---# Git Commit (TroubleScout)Use this skill when you need to turn working changes into one or more high-signal commits.## Inputs to gather- What was the intent of the change? (bug fix vs behavior change vs docs vs build/packaging)- Which areas are touched? (CLI entry, Copilot session behavior, PowerShell execution/safety, UI output, tools)- Is anything sensitive present in diffs? (tokens, hostnames, IPs, event log contents, stack traces with secrets)## Workflow1. Confirm you are not on `main`.2. Review the working tree (`git status -sb`) and inspect the diff (`git diff`).3. Split unrelated changes into separate commits.4. Stage intentionally: - Prefer `git add -p` for mixed files. - Avoid staging generated build output (`bin/`, `obj/`) unless explicitly requested.5. If `.cs` files changed, run `dotnet build` before committing.6. Write an emoji-prefixed commit subject line: - Format: `<emoji> <summary>` - Keep it short and specific; use imperative mood.7. Commit without bypassing hooks (do not use `--no-verify`).## Emoji prefixesCommit subjects must start with an emoji. Use any emoji; these are common conventions:- ✨ New behavior / feature- 🐛 Bug fix- ♻️ Refactor- 📝 Docs- 🔧 Build/config- ✅ Tests- 🔖 Release/tagging## Message examples- ✨ Add WinRM connectivity check- 🐛 Fix null handling in Copilot delta events- 🔧 Update publish defaults for win-x64- 📝 Clarify release packaging instructions## Safety checks- Do not commit secrets (tokens, credentials), personal data, or sensitive server data.- If logs are required, redact/trim to the minimal necessary context.- Never force-push. Never rewrite published history.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/sasler) — claim your Tome and manage your conversions.

Frequently asked questions