Agent skill
commit-code
Commit code following HMIS project conventions. Use when committing changes with proper issue closing keywords, message format, and co-author attribution.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/commit-code
SKILL.md
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 <[email protected]>
Issue Closing Keywords
Closes #N- for general issue resolutionFixes #N- for bug fixesResolves #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
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?