commit-code

What it does and when to use it

Commit code following HMIS project conventions. Use when committing changes with proper issue closing keywords, message format, and co-author attribution.

Arguments

/commit-code [issue-number]

How it works

1. Arguments
2. Commit Message Format
3. Issue Closing Keywords
4. Steps
5. Rules
6. After Every Push

---
name: commit-code
description: >
  Commit code following HMIS project conventions. Use when committing changes with
  proper issue closing keywords, message format, and co-author attribution.
disable-model-invocation: true
allowed-tools: Bash, Read, Grep
argument-hint: "[issue-number]"
---

# 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

```
<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

1. Run `git status` to see what's staged
2. Run `git diff --staged` to review changes
3. Compose commit message following the format above
4. If issue number provided, include closing keyword
5. Commit with the formatted message
6. 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

## After Every Push

After every successful `git push`, **immediately** restore the local JNDI names in `persistence.xml`
— swap `${JDBC_DATASOURCE}` and `${JDBC_AUDIT_DATASOURCE}` back to whatever local names were
there before (e.g. `jdbc/ruhunu` and `jdbc/ruhunuAudit`). Leave the change unstaged.
This lets the developer run and test without any manual step.

Versions

Database snapshot: 13.11.2026 · package version 51337e7c8878 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

• 100commit
  ALWAYS use this skill when committing code changes — never commit directly without it. Creates commits following Sentry conventions with proper conventional commit format and issue references. Trigger on any commit, git commit, save changes, or commit message task.
• 100commit
  ALWAYS use this skill when committing code changes — never commit directly without it. Creates commits following Sentry conventions with proper conventional commit format and issue references. Trigger on any commit, git commit, save changes, or commit message task.
• 90review-code
  Review code changes following HMIS project standards. Use when reviewing a pull request, verifying code changes, or checking code quality. Covers CodeRabbit verification, backward compatibility, persistence checks, and project-specific patterns.
• 100commit
  Creates commits with Conventional Commits format (feat/fix/docs/refactor/test/chore), scope detection, co-author attribution, and pre-commit hook compliance. Validates staged changes and prevents secrets or generated-only files from being committed. Use for requests to commit,…
• 100commit
  Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.
• 100commit
  Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes or mentions "/commit".