菜单
Verify and manage persistence.xml configuration around git push. Use before pushing to ensure environment variable placeholders are in place, and after pushing to restore local JNDI names for continued testing. Prevents QA deployment failures from hardcoded datasource names.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
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 | verify-persistence |
| description | Verify and manage persistence.xml configuration around git push. Use before pushing to ensure environment variable placeholders are in place, and after pushing to restore local JNDI names for continued testing. Prevents QA deployment failures from hardcoded datasource names. |
| disable-model-invocation | true |
| allowed-tools | Read, Grep, Bash, Edit |
Manage src/main/resources/META-INF/persistence.xml across the push workflow.
[Local dev] jdbc/ruhunu → [pre-push] swap to placeholders → git push → [post-push] swap back to jdbc/ruhunu
Read persistence.xml — note the current <jta-data-source> values in both
hmisPU and hmisAuditPU units. If they are already placeholders, nothing to do.
If hardcoded JNDI names are present (e.g. jdbc/ruhunu, jdbc/coop):
jdbc/... → ${JDBC_DATASOURCE} (main unit)jdbc/...Audit → ${JDBC_AUDIT_DATASOURCE} (audit unit)Check DDL generation paths — must NOT contain hardcoded paths:
eclipselink.application-location with c:/tmp/ or /home/*/tmp/Immediately after every git push, restore the JNDI names that were there before:
${JDBC_DATASOURCE} → the original local JNDI name (e.g. jdbc/ruhunu)${JDBC_AUDIT_DATASOURCE} → the original local audit JNDI name (e.g. jdbc/ruhunuAudit)Leave this change unstaged — never commit or push local JNDI names.
Confirm to the user: persistence.xml restored to local JNDI for testing.
Why: The developer needs to run and test immediately after every push. Without this step they have to manually revert persistence.xml every time, which is unnecessary friction.
| Setting | Deployment-ready (push) | Local dev (test) |
|---|---|---|
| Main datasource | ${JDBC_DATASOURCE} | jdbc/coop, jdbc/ruhunu, etc. |
| Audit datasource | ${JDBC_AUDIT_DATASOURCE} | jdbc/ruhunuAudit, etc. |
| DDL location | Not present or env var | c:/tmp/, /home/buddhika/tmp/ |