← ClaudeAtlas

publishlisted

Publish the app to its own web address on tirohealth.app and report the URL. Use when the clinician asks to publish, deploy, go live, share the app, or wants the latest version online.
Tiro-health/ehr-app-for-mds · ★ 0 · Data & Documents · score 70
Install: claude install-skill Tiro-health/ehr-app-for-mds
# Publish The app is published at `https://<app>.tirohealth.app`, where `<app>` is the name Tiro approved it under. Publishing is done by **Tiro Deploy**, a GitHub App installed on this repository: on every push to `main` it checks the app is approved, builds it and puts it online. It reports the result as a check called **Tiro Deploy (production)** on the pushed commit. Everything here needs `gh`, logged in (`gh auth status`). If it is missing, install it and run `gh auth login` with the clinician, explaining in one sentence that it lets you publish for them. ## 1. Check and push 1. Run `pnpm check`. Fix anything it reports; never publish a broken build. 2. Make sure all work is committed on `main`. Commit with a plain-language message if not. 3. `git push origin main`. ## 2. Wait for Tiro Deploy's check Get the owner and repository from `git remote -v` and the commit with `git rev-parse HEAD`, then poll every 15 seconds, for up to 15 minutes, until the check is completed: ```bash gh api repos/<owner>/<repo>/commits/<sha>/check-runs \ --jq '.check_runs[] | select(.app.slug == "tiro-health-deploy") | {status, conclusion, title: .output.title, summary: .output.summary, url: .details_url, log: .output.text}' ``` A build usually takes two to four minutes. Tell the clinician it is on its way while you wait. ## 3. Act on the result - **No Tiro Deploy check appears within a minute**: Tiro Deploy is not installed on this repository. Ask the clinician to open https://gi