skills.rest
withmartian-sandbox
withmartian-sandboxOFFICIAL
Explore all skills by this author →
GitHub

commit-code

Generate standardized HMIS commit messages with closing keywords and co-authorship.

Updated Aug 23, 2026
Search Tags:#git#commit#conventions#code-quality#hmis
One-click install
npx skills add https://github.com/withmartian-sandbox/ghrc-x-a78d77e2f0a84f43b4d486d418566b5b --skill commit-code-withmartian-sandbox
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-code
Source: https://github.com/withmartian-sandbox/ghrc-x-a78d77e2f0a84f43b4d486d418566b5b/tree/main/.claude/skills/commit-code
Command: npx skills add https://github.com/withmartian-sandbox/ghrc-x-a78d77e2f0a84f43b4d486d418566b5b --skill commit-code-withmartian-sandbox

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

HMIS projects often suffer from inconsistent commit messages, poor traceability, and missing attribution. This skill enforces a standardized commit message format to improve history quality and collaboration.

Core Features & Use Cases

  • Enforces a consistent HMIS commit message structure with subject, body, and closing keywords.
  • Adds Co-Authored-By attribution to commits and prevents accidental unsafe changes from being pushed.
  • Supports standard issue keywords like Closes, Fixes, and Resolves to ensure proper linkage to issues.

Quick Start

Generate a properly formatted commit message for your staged changes following HMIS conventions.

Frequently Asked Questions about commit-code

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

FAQPage Schema
How do I enforce HMIS commit conventions for git messages?▼

Enforcing HMIS commit conventions involves automating standardized commit messaging with a proper structure for subject, body, and closing keywords. This ensures consistent history, proper attribution, and traceability across HMIS modules.

What is the standard structure for an HMIS commit message?▼

The standard HMIS commit message structure consists of a subject, a body, and issue-tracking closing keywords like Closes, Fixes, or Resolves. It also requires Co-Authored-By attribution to maintain proper history and collaboration traceability.

How do I add Co-Authored-By attribution to my git commits?▼

Adding Co-Authored-By attribution to git commits is handled automatically by enforcing HMIS commit conventions. This ensures proper credit is recorded within the structured message format and prevents accidental unsafe code changes from being pushed.

Can I use standard issue keywords like Closes and Fixes in HMIS projects?▼

Yes, HMIS projects support standard issue keywords such as Closes, Fixes, and Resolves within the commit message structure. Using these closing keywords ensures proper issue linkage and traceability across feature, bugfix, and documentation updates.

How do I prevent accidental unsafe changes from being pushed in git?▼

Preventing accidental unsafe changes from being pushed is achieved by enforcing HMIS commit conventions. By standardizing the commit message structure and validating closing keywords, the workflow blocks unsafe modifications from entering the project history.

Related Skills

Explore More Software Engineering Skills→
hmislkhmislk
224

commit-code

Generate HMIS-compliant commit messages with issue closing keywords and co-author attribution.

Official
Intermediate
glhewettglhewett

issues-close

Close TOML issues by updating metadata, appending comments, and committing.

Community
Intermediate
proven-xyzproven-xyz
2

commit

Generate standardized git commit messages from diffs using Conventional Commits rules.

Official
Advanced
aldy505aldy505

commit

Generate Git commit messages following Sentry conventional commit standards.

Community
Intermediate