Provider Verification
mondoohq/mql
Verify mql provider resource/field changes against real cloud infrastructure.
Sync development into QA/testing environment branches (QA1-QA4, local RH staging) via PR + merge on GitHub.
$ npx skills add hmislk/hmis --skill deploy-qa -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install hmislk/hmis deploy-qa --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/hmislk/hmis.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/deploy-qa .claude/skills/deploy-qa && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "deploy-qa" agent skill from https://github.com/hmislk/hmis/tree/development/.claude/skills/deploy-qa into .claude/skills/deploy-qa/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploy-qa", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/hmislk/hmis/tree/development/.claude/skills/deploy-qaType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add hmislk/hmis --skill deploy-qa -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install hmislk/hmis deploy-qa --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hmislk/hmis.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/deploy-qa .agents/skills/deploy-qa && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "deploy-qa" agent skill from https://github.com/hmislk/hmis/tree/development/.claude/skills/deploy-qa into .agents/skills/deploy-qa/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploy-qa", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add hmislk/hmis --skill deploy-qa -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install hmislk/hmis deploy-qa --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hmislk/hmis.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/deploy-qa .cursor/skills/deploy-qa && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "deploy-qa" agent skill from https://github.com/hmislk/hmis/tree/development/.claude/skills/deploy-qa into .cursor/skills/deploy-qa/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploy-qa", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/hmislk/hmis.git --path .claude/skills/deploy-qa--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add hmislk/hmis --skill deploy-qa -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install hmislk/hmis deploy-qa --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hmislk/hmis.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/deploy-qa .gemini/skills/deploy-qa && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "deploy-qa" agent skill from https://github.com/hmislk/hmis/tree/development/.claude/skills/deploy-qa into .gemini/skills/deploy-qa/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploy-qa", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install hmislk/hmis deploy-qaInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add hmislk/hmis --skill deploy-qa -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/hmislk/hmis.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/deploy-qa .github/skills/deploy-qa && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "deploy-qa" agent skill from https://github.com/hmislk/hmis/tree/development/.claude/skills/deploy-qa into .github/skills/deploy-qa/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploy-qa", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add hmislk/hmis --skill deploy-qa -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install hmislk/hmis deploy-qa --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hmislk/hmis.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/deploy-qa .opencode/skills/deploy-qa && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "deploy-qa" agent skill from https://github.com/hmislk/hmis/tree/development/.claude/skills/deploy-qa into .opencode/skills/deploy-qa/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploy-qa", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
deploy-qaSync development into QA/testing environment branches (QA1-QA4, local RH staging) via PR + merge on GitHub.
Deploy QA is an agent skill from hmislk/hmis. Sync development into QA/testing environment branches (QA1-QA4, local RH staging) via PR + merge on GitHub. Use when deploying/promoting the latest development code to any HMIS QA instance or the local RH staging environment.
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering QA and bug reports. It works with Microsoft Azure and GitHub. The repository describes itself as: This is an Open Source Java EE based Hospital Information Management System. The licence is GPL-3.0.
3 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit d5d2020. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
BashReadGrepFrom allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
ghgitFrom the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
github.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Deploy QA loads about 2.1k tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 852 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
allowed-tools: Bash, Read, GrepAutomated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from hmislk/hmis at commit d5d2020, republished under its GPL-3.0 licence (© hmislk). 852 words, ~2,077 tokens.
.claude/skills/deploy-qa/SKILL.md (or your agent's skills folder).QA1-QA4 moved off the Azure "migrated" estate onto home-hosted machines
starting 2026-09-12 (tracked in the private
hmislk/qa-home-infra repo —
MASTER-PLAN.md for status, GOTCHAS.md for detail). The plan is to
retire the Azure targets entirely once cutover completes — there will be
no more Azure QA environments. qa1-qa4 below now mean the home
instances; the old Azure branches are kept only as *-azure arguments
until the qa-home-infra Cutover checklist is fully ticked, at which point
this skill should be edited again to remove the *-azure section outright.
rh-local is unaffected by any of this — same branch, same workflow, no
change.
| Argument | Target branch | Notes |
|---|---|---|
qa1 | home-qa1 | hiu-laptop / carecode account — self-hosted runner qa1 |
qa2 | home-qa2 | hiu-laptop / buddhika account — self-hosted runner qa2 |
qa3 | home-qa3 | Desktop (Windows) — self-hosted runner qa3; Desktop also runs nginx for all four public hostnames |
qa4 | home-qa4 | carecode-laptop (Windows) — self-hosted runner qa4 |
rh-local | rh-local-staging | Local RH staging — does NOT share prod's ruhunu DB, unaffected by the QA migration |
all | all four home-qaN + rh-local-staging | Run each independently; one failing doesn't block the rest |
qa1-azure … qa4-azure (deprecated) | hims-qa1-migrated … hims-qa4-migrated | Legacy Azure estate. Use only if a home instance is genuinely unreachable. Will be deleted from this skill once qa-home-infra's Cutover checklist is complete. |
Do not use the bare non--migrated/non-home- hims-qa* branches, and
never target hims-qaN-home (singular, no trailing -migrated/-azure) —
that pattern collides with the repo's "QA Branches Rules" ruleset (PR-only
pushes + a check-branch status check that's only ever attached via a PR),
so a branch under it can never even be created by a direct push. The
correct home branch name is home-qaN, not hims-qaN-home.
qa1-qa4, default)Home branches carry no branch protection (that's deliberate — see the
naming note above), and they only ever exist to mirror development and
fire the deploy workflow on push. There is no PR/merge step and no
check-branch wait:
git fetch origin
# Mirror development onto the target home branch. --force-with-lease is
# safe here even though these branches have no protection: it just means
# the push aborts (instead of silently clobbering) if someone else moved
# the branch since your last fetch.
git push origin origin/development:home-qa1 --force-with-leaseIf it prints Everything up-to-date, the branch already matches
development — nothing to deploy, skip it (same idea as the Azure flow's
"No commits between X and development").
The push itself triggers hims_qa1_home_ci_cd.yml (swap the number for
qa2/qa3/qa4). Watch it:
gh run list --repo hmislk/hmis --workflow=hims_qa1_home_ci_cd.yml --limit 1
gh run watch --repo hmislk/hmis <run-id> --exit-statusEach home workflow builds and deploys in one job, entirely on that
machine's own self-hosted runner (labels qa1/qa2/qa3/qa4) — no
artifact upload/download, so a deploy is a couple of minutes end to end,
not the 20-30 minutes an artifact-transfer design costs over a home
connection (measured and fixed per-instance; see qa-home-infra's
GOTCHAS.md § "deploys take ~30 min on a home link" if a home-qaN workflow
still shows the old split-job design — it should have been migrated to the
local-build pattern already, but if not, that section has the fix).
Each workflow keeps its own rollback copy of the previously-deployed WAR and auto-restores it if the new deploy or its health check fails — no manual rollback step needed on a failed run, but do read the run's log if one fails rather than assuming it self-healed correctly.
qa1-azure … qa4-azure)Same PR + merge flow as before this migration:
git fetch origin
# 1. Dry-run the merge to catch conflicts before opening a PR
git merge-tree --write-tree origin/hims-qa1-migrated origin/development
# exit code 0 with a tree hash = clean; non-zero / "CONFLICT" text = stop and
# resolve manually before proceeding
# 2. Open the sync PR (development -> target branch)
gh pr create --repo hmislk/hmis --base hims-qa1-migrated --head development \
--title "chore(sync): merge development into hims-qa1-migrated" \
--body "Syncs the hims-qa1-migrated QA/testing environment branch with the latest development. QA/testing-only branch — safe to merge."
# If it fails with "No commits between X and development", the branch is
# already in sync — nothing more to do for it.
# 3. Confirm CI passed before merging
gh pr checks <PR-number> --repo hmislk/hmis
# 4. Merge (regular merge commit, keep both branches)
gh pr merge <PR-number> --repo hmislk/hmis --merge --delete-branch=falseGitHub Actions then builds with Maven, deploys to the Azure estate, and
restarts Payara. The four migrated workflows use a per-branch concurrency
group, so deploying several in one deploy-qa all run doesn't cancel each
other.
If a hims-qaN-migrated branch has drifted such that a development-headed
PR shows a merge conflict, the fix is not a conflict-resolution branch —
check-branch (branch_merge_validation.yml) only allows development as
the PR head for a hims-qa*-migrated base, so such a PR always fails CI. An
admin must reconcile it: temporarily add a bypass actor to the QA Branches Rules ruleset (id 4778267), then
git fetch origin && git push --force-with-lease origin origin/development:hims-qaN-migrated
(lease-protected so a concurrent update to the target branch aborts the push
instead of being silently discarded), then restore the ruleset to
bypass_actors: [].
http://localhost:9080/qa1 for QA1 — the
public qaN.carecode.org URL additionally depends on the Desktop's nginx
being correctly wired for that instance)qa-home-infra's
GOTCHAS.md if login fails after an otherwise-green deploy)If a home-target deployment fails:
gh run view <run-id> --log-failed) —
the run happened entirely on that machine's self-hosted runner, so the
failure is local (JDBC pool unreachable, Payara admin port down, disk
full), not a generic cloud CI issuegh api repos/hmislk/hmis/actions/runners --jq '.runners[] | {name, status}'qa-home-infra's GOTCHAS.md and the relevant machine's runbooks/
file are the first place to check for a known issueIf a legacy Azure-target deployment fails:
src/main/resources/META-INF/persistence.xml uses ${JDBC_DATASOURCE} /
${JDBC_AUDIT_DATASOURCE} on these branches (not a hardcoded local JNDI name)© hmislk, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .claude/skills/deploy-qa of hmislk/hmis.
Open the folder on GitHubat commit d5d2020
Deploy QA next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Deploy QA this skillhmislk/hmis | 236 | — | ~2.1k | Automated safety check: Notes | GPL-3.0 | |
| Provider Verificationmondoohq/mql | 411 | — | ~3.7k | Automated safety check: Pass | Custom licence | |
| Azureml K3s Compute Target Setupmicrosoft/physical-ai-toolchain | 123 | — | ~5.7k | Automated safety check: Notes | MIT | |
| Testing Course Samplesmicrosoft/ai-agents-for-beginners | 77k | — | ~1.1k | Automated safety check: Notes | MIT | |
| Testing Course Samplesmicrosoft/ai-agents-for-beginners | 77k | — | ~1.3k | Automated safety check: Notes | MIT | |
| Testing Course Samplesmicrosoft/ai-agents-for-beginners | 77k | — | ~1.3k | Automated safety check: Notes | MIT |
mondoohq/mql
Verify mql provider resource/field changes against real cloud infrastructure.
microsoft/physical-ai-toolchain
Set up a K3s cluster on an NVIDIA GPU host, connect it to Azure Arc, and configure Azure ML to use it as a Kubernetes compute target.
microsoft/ai-agents-for-beginners
A skill your agent uses when asked to validate, test, smoke-test, or run the course's notebook and code samples against a live Microsoft Foundry / Azure OpenAI configuration.
microsoft/ai-agents-for-beginners
Koristite kada se zatraži validacija, testiranje, smoke-test ili pokretanje bilježnica i primjera koda tečaja protiv aktivne Microsoft Foundry / Azure OpenAI konfiguracije.
microsoft/ai-agents-for-beginners
Use wen dem ask you to validate, test, smoke-test, or run di course notebook and code samples against live Microsoft Foundry / Azure OpenAI configuration.
microsoft/ai-agents-for-beginners
Gamitin kapag hiniling na i-validate, subukan, smoke-test, o patakbuhin ang notebook ng kurso at mga halimbawa ng code laban sa isang live na Microsoft Foundry / Azure OpenAI na configuration.
hmislk/hmis
Reference for calling existing HMIS REST APIs. An agent skill from hmislk/hmis.
hmislk/hmis
Application configuration options reference for the HMIS project.
hmislk/hmis
Ultra-compressed communication mode. An agent skill from hmislk/hmis.
hmislk/hmis
MySQL database development guide for the HMIS project. An agent skill from hmislk/hmis.
hmislk/hmis
A skill your agent uses when asked to make a demo, training, how-to or tutorial video with sound or voice-over showing an HMIS function or configuration (e.g.
hmislk/hmis
Run a GitHub issue through its full lifecycle end-to-end: investigate, discuss the approach, gather test context (department/data), implement, rebuild + local redeploy, verify with Playwright and…
Works with
Categories
Sync development into QA/testing environment branches (QA1-QA4, local RH staging) via PR + merge on GitHub. Deploy QA is an agent skill from hmislk/hmis. Sync development into QA/testing environment branches (QA1-QA4, local RH staging) via PR + merge on GitHub.
Deploy QA fits situations like: deploying/promoting the latest development code to any HMIS QA instance; the local RH staging environment.
Run `npx skills add hmislk/hmis --skill deploy-qa -a claude-code`. Or copy the skill folder (.claude/skills/deploy-qa in hmislk/hmis) into .claude/skills/deploy-qa in your project. Claude Code loads it when a task matches its description.
Run `npx skills add hmislk/hmis --skill deploy-qa -a codex`. Or copy the skill folder (.claude/skills/deploy-qa in hmislk/hmis) into .agents/skills/deploy-qa in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hmislk/hmis --skill deploy-qa -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/deploy-qa, .gemini/skills/deploy-qa, .github/skills/deploy-qa and .opencode/skills/deploy-qa in your project.
Going by SKILL.md and its folder, Deploy QA needs the command-line tools its instructions call (gh and git). Its frontmatter pre-approves these tools: Bash, Read, Grep.
SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Deploy QA is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.1k tokens (SKILL.md is roughly 8.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Deploy QA: Provider Verification (mondoohq/mql, 411 stars), Azureml K3s Compute Target Setup (microsoft/physical-ai-toolchain, 123 stars), Testing Course Samples (microsoft/ai-agents-for-beginners, 77k stars) and Testing Course Samples (microsoft/ai-agents-for-beginners, 77k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
hmislk (a GitHub organization) maintains it in hmislk/hmis, which has 236 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on October 8, 2026.
Source: hmislk/hmis on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.