skills.rest
hmislk
hmislkOFFICIAL
Explore all skills by this author →
WebsiteGitHub

commit-code

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

224|136|Updated Jul 12, 2014
Search Tags:#git#commit#message-format#co-author#hmis#closing-keywords
One-click install
npx skills add https://github.com/hmislk/hmis --skill commit-code
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-code
Source: https://github.com/hmislk/hmis/tree/main/.claude/skills/commit-code
Command: npx skills add https://github.com/hmislk/hmis --skill commit-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineering teams maintain consistent, HMIS-compliant commit messages across the codebase, ensuring clear history, proper issue closing, and proper attribution.

Core Features & Use Cases

  • Enforces HMIS commit message format including Closes/Fixes/Resolves keywords.
  • Supports optional issue number and Co-Authored-By attribution.
  • Audits staged changes and prevents pushing non-compliant messages.

Quick Start

Use the commit-code workflow to craft and apply a properly formatted commit message for your staged changes.

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 message format with closing keywords and co-author attribution?▼

To enforce HMIS commit message format, you can use an automated workflow that audits staged Git changes and applies messages containing Closes, Fixes, or Resolves keywords alongside the Co-Authored-By line.

What is the required format for HMIS project commit messages?▼

The required HMIS commit message format mandates specific closing keywords like Closes, Fixes, or Resolves, and includes a Co-Authored-By attribution to ensure clear project history and proper issue tracking.

How do I add Co-Authored-By and issue closing keywords to my staged Git changes?▼

You can add Co-Authored-By and closing keywords to staged Git changes by running an automated commit workflow that validates your staged environment and formats the message automatically.

Do I need a staged Git environment and issue number to automate HMIS commit messages?▼

Yes, you need a staged Git environment to automate HMIS commit messages, while an issue number is optional but recommended for properly linking the commit to the issue it resolves.

Why does my commit message get rejected when pushing to HMIS repositories?▼

Your commit message gets rejected from HMIS repositories if it lacks the required Closes, Fixes, or Resolves keywords and the Co-Authored-By line, as the system audits staged changes to prevent non-compliant pushes.

Related Skills

Explore More Software Engineering Skills→
navidemadnavidemad

publish

Generate conventional commit messages and GitHub pull request descriptions.

Community
Intermediate
cbbkrd-techcbbkrd-tech

ln-003-push-all

Commit and push all local changes to the remote repository.

Community
Intermediate
Marshall-HallenbeckMarshall-Hallenbeck
5

safe-commit-all

Group working-tree changes into conventional git commits with issue references.

Community
Intermediate
FullFranFullFran
1

commit-convention

Enforce Conventional Commits format for git commit messages.

Community
Intermediate