gh-init
Bootstrap/verify GitHub CLI auth ("set up gh", "check gh auth", "is gh logged in"). Not PR ops or Jira setup.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 15
- Forks
- 2
01 前言 Front Matter
- name
- gh-init
- description
- Bootstrap/verify GitHub CLI auth ("set up gh", "check gh auth", "is gh logged in"). Not PR ops or Jira setup.
03 SKILL.md 正文
gh-init
The user wants to verify forge auth (or wants instructions to log in).
Run /gh-init. It detects the forge from the origin remote (defaulting to GitHub): on a GitHub repo it verifies gh auth + scopes; on a Bitbucket repo it checks the himmel bitbucket CLI auth (BITBUCKET_EMAIL + BITBUCKET_API_TOKEN) instead of gh OAuth scopes.
Output the single one-line summary the slash command prints. If it exits non-zero with gh NOT logged in, tell the user to run gh auth login --web from their own terminal — that flow is interactive (browser) and cannot be automated. If it exits non-zero with bitbucket NOT authenticated, tell the user to set BITBUCKET_EMAIL + BITBUCKET_API_TOKEN.
04 同仓库更多 Skills
medic
Use inside a Salus medical vault to FILE a medical item into its structured place (skin photo → photo archive + capture note; lesion/symptom note; lab/PDF → 00-Sources) and auto-commit, OR to QUERY the vault for a health follow-up (grounded answer + flagged, non-diagnostic morphology read). Triggers on "file this photo / note / lab", "log this into the medical vault", "ask the medic", or any health follow-up while cwd = the medical vault. Organize & surface only — never diagnose (posture-A).
stuck-playbook
fixture skill, invoked in the basic transcript fixture
never-used-skill
fixture skill, never invoked in any fixture transcript
used-skill
fixture skill invoked via a Skill tool_use in the fixture transcript
dead-skill
fixture skill never invoked and never referenced
jira-transition
Move/transition a Jira issue status ("move PROJ-46 to In Progress"). Needs key + target status. Not PR status changes.