git-commits_skill

This skill standardizes git commits by prefixing messages with the current hostname and type, ensuring traceable history across the project.

JavaScript

0

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill splitleaseteam/splitlease_monorepo --skill git-commits

SKILL.md4.8 KB

Overview

This skill standardizes git commit messages for the Split Lease app by enforcing a prefixed format: [hostname][type] commit message. It ensures every commit includes the actual device hostname (run via hostname) for traceability across the team. The result is consistent, searchable commit history and clearer ownership of changes.

How this skill works

Before creating any commit, the skill requires running the hostname command and using its exact output as the <HOSTNAME> prefix. You then pick a conventional commit type (feat, fix, docs, chore, refactor, test, style, perf, revert) and write a concise imperative message. For multi-line commits or co-authored commits, use a heredoc and include the hostname in the first line.

When to use it

Every git commit operation in the Split Lease repo
When asked to "commit changes" or automating commit hooks
For single-file commits and multi-file changes with body text
When adding co-authors or detailed commit bodies (use heredoc)
During CI jobs that create commits, after retrieving the runtime hostname

Best practices

Always run hostname first and copy the exact output — never hardcode or guess it
Choose the correct conventional type (feat, fix, docs, chore, refactor, test, style, perf, revert)
Write short, imperative summaries (use present tense: add, fix, update)
Use heredoc for multi-line commit bodies and to append Co-Authored-By lines
Include only one clear purpose per commit when possible to simplify history and review

Example use cases

Local feature work: run hostname then git commit -m "[HOST-123][feat] add proposal submission workflow"
Bug fix: run hostname then git commit -m "[HOST-123][fix] resolve FK constraint error in listing updates"
Documentation change: hostname + git commit -m "[HOST-123][docs] update CONTRIBUTING and CLAUDE notes"
Multi-file feature with details: use hostname and heredoc to include a bullet list of changed components
Automated commit in CI: retrieve container/runner hostname programmatically then format commit message accordingly

FAQ

Do not commit. Run hostname, copy its exact output, then recreate the commit message using that value. Never use guessed hostnames.

How do I include co-authors or a multi-line body?

Run hostname, then use a heredoc in git commit -m "$(cat <<'EOF' ... EOF)" with the first line containing [<HOSTNAME>][<type>] and Co-Authored-By lines in the body.