メニュー
Commit code following HMIS project conventions. Use when committing changes with proper issue closing keywords, message format, and co-author attribution.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/hmislk/hmis --skill commit-codeコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Run a live bug-demonstration capture session before filing GitHub issues. The user drives the browser and narrates bugs one after another ("see this — clicking X should do Y but does Z"); this skill captures each demo (snapshot + screenshot + description + environment context) without investigating, only after the user signals the session is over does it investigate root causes, then only after the user reviews the write-ups does it file issues. Use when asked to "demonstrate some bugs", "show you issues before filing them", or via `/demonstrate-issues`. Never fixes anything — it ends at filing GitHub issue(s); any actual fix is separate, later `dev-issue` work.
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 the database, iterate until passing, record any testing-workflow learnings, commit/push, open a PR, and loop on review comments until mergeable. Use when asked to "take issue #N end to end", "do issue #N fully", "develop and ship issue #N", or similar full-cycle requests.
Run one or more GitHub issues through their full lifecycle end-to-end with NO pauses for user input — investigate, decide the approach, gather test context, and run the CI/review loop entirely autonomously, documenting every judgment call for after-the-fact review instead of asking. Accepts a single issue, a batch of issue numbers/URLs, or an unfiled bug/request described in plain text. Use ONLY when the user has explicitly said they will be unreachable (away from the computer, asleep, offline) and wants the issue(s) shipped as mergeable PR(s) without them. Do not use this for normal work — use dev-issue instead, which asks for input at the same points this skill auto-resolves.
SOC 職業分類に基づく
SKILL.md を表示中
| name | commit-code |
| description | Commit code following HMIS project conventions. Use when committing changes with proper issue closing keywords, message format, and co-author attribution. |
| disable-model-invocation | true |
| allowed-tools | Bash, Read, Grep |
| argument-hint | [issue-number] |
Commit staged changes following the project's commit message conventions.
$0 - GitHub issue number (optional, for closing keyword)<Summary of change in imperative mood>
Closes #<issue-number>
Co-Authored-By: Claude <noreply@anthropic.com>
Closes #N - for general issue resolutionFixes #N - for bug fixesResolves #N - alternative to closesgit status to see what's stagedgit diff --staged to review changesAfter every successful git push, immediately restore the local JNDI names in persistence.xml
— swap ${JDBC_DATASOURCE} and ${JDBC_AUDIT_DATASOURCE} back to whatever local names were
there before (e.g. jdbc/ruhunu and jdbc/ruhunuAudit). Leave the change unstaged.
This lets the developer run and test without any manual step.