القائمة
Commit code following HMIS project conventions. Use when committing changes with proper issue closing keywords, message format, and co-author attribution.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
REST API development guide for the HMIS project. Use when creating or extending any REST API endpoint — covers file structure, auth pattern, response format, ApplicationConfig registration, CapabilityStatementResource update, AnthropicApiService integration (system prompt module + tool handler), and the full post-implementation checklist.
Pharmacy module development guide for the HMIS project. Use when working on pharmacy features including GRN, purchase orders, stock transfers, disbursements, retail sales, pharmacy reports, stock management, item substitution, or pharmacy billing workflows.
REST API development guide for the HMIS project. Use when creating or extending any REST API endpoint — covers file structure, auth pattern, response format, ApplicationConfig registration, CapabilityStatementResource update, AnthropicApiService integration (system prompt module + tool handler), and the full post-implementation checklist.
Pharmacy module development guide for the HMIS project. Use when working on pharmacy features including GRN, purchase orders, stock transfers, disbursements, retail sales, pharmacy reports, stock management, item substitution, or pharmacy billing workflows.
HMIS UI development guidelines for JSF/XHTML pages. Use when creating or modifying XHTML pages, PrimeFaces components, page layouts, forms, buttons, panels, datatables, or any frontend/UI work. Covers page structure, layout patterns, panel best practices, form inputs, button styling, responsive design, and accessibility rules.
Application configuration options reference for the HMIS project. Use when working with feature toggles, configuration keys, configOptionApplicationController, bill number configuration, printer configuration, or any configurable application behavior.
| 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 staged changes following the project's commit message conventions.
$0 - GitHub issue number (optional, for closing keyword)<Summary of change in imperative mood>
Closes #<issue-number>
Co-Authored-By: Claude <noreply@anthropic.com>
Closes #N - for general issue resolutionFixes #N - for bug fixesResolves #N - alternative to closesgit status to see what's stagedgit diff --staged to review changesAfter 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.