// 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.
| 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/ |
Handle CodeRabbit and Codex review comments on a GitHub PR. Fetches the PR, investigates each comment against the codebase, discusses validity with the user, batches valid fixes, and guides through push and reply steps.
Investigate and resolve GitHub pull request review comments for HMIS. Use when the user wants Codex to read PR review threads, assess CodeRabbit or Codex feedback, discuss valid fixes, batch and apply changes, reply to each comment, and re-request review.
JSF AJAX update rules for the HMIS project. Use when working on AJAX updates, p:commandButton update attributes, PrimeFaces AJAX callbacks, partial page rendering, or debugging AJAX update failures. Also covers JSF navigation patterns: why f:viewAction must not be used on @SessionScoped beans, and how initialization belongs in navigation methods. Critical rules to prevent silent AJAX failures and refresh/back-button state corruption.
JSF AJAX update rules for the HMIS project. Use when working on AJAX updates, p:commandButton update attributes, PrimeFaces AJAX callbacks, partial page rendering, or debugging AJAX update failures. Also covers JSF navigation patterns: why f:viewAction must not be used on @SessionScoped beans, and how initialization belongs in navigation methods. Critical rules to prevent silent AJAX failures and refresh/back-button state corruption.
Commit code following HMIS project conventions. Use when committing changes with proper issue closing keywords, message format, and co-author attribution.
Full environment setup when starting work on a GitHub issue. Creates a feature branch from origin/development, swaps persistence.xml to local JNDI settings, assigns the issue, and guides project board setup. Use when beginning work on any new issue: "start issue 20408", "/start-issue 20408", or "prepare env for issue 20408".