Commit Code with HMIS Conventions
Commit staged changes following the project's commit message conventions.
Arguments
- •
$0- GitHub issue number (optional, for closing keyword)
Commit Message Format
code
<Summary of change in imperative mood> Closes #<issue-number> Co-Authored-By: Claude <noreply@anthropic.com>
Issue Closing Keywords
- •
Closes #N- for general issue resolution - •
Fixes #N- for bug fixes - •
Resolves #N- alternative to closes
Steps
- •Run
git statusto see what's staged - •Run
git diff --stagedto review changes - •Compose commit message following the format above
- •If issue number provided, include closing keyword
- •Commit with the formatted message
- •Report the commit hash and summary
Rules
- •NEVER push unless explicitly asked
- •NEVER amend previous commits unless explicitly asked
- •Check persistence.xml - if it's in the staged files, verify it uses environment variables
- •No credentials - warn if .env or credentials files are staged
- •JSF-only changes (XHTML only, no Java) do not require compilation