メニュー
Open a pull request in this repo — branch naming, title format, and the required description sections. Use when the user asks to create, open, or prep a PR.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/rhesis-ai/rhesis --skill pull-requestコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Colour, font and design-token rules for the docs site — when hex is banned, when it is correct, and which surfaces ignore the theme. Use when styling docs components or editing CSS under docs/src.
How the docs site generates per-page og:image cards, and the cache and font traps when changing them. Use when editing the OG card design, og-theme.js, or a page's social preview image.
Add a new Enterprise Edition feature behind a feature gate, across backend and frontend. Use when adding an EE-only capability such as SSO.
| name | pull-request |
| description | Open a pull request in this repo — branch naming, title format, and the required description sections. Use when the user asks to create, open, or prep a PR. |
An open PR is not a standing approval for more commits. Once a PR exists, every additional
commit or push to it — including small fixes requested after review — needs its own go-ahead
from the user before you run git commit/git push, same as the first one.
Small PRs, one logical change each. Ideal 1-200 lines, acceptable 200-400, break down 400+.
Branch from latest main: git fetch origin && git checkout main && git pull origin main && git checkout -b feature/your-feature-name.
Title: action verb first (Add/Fix/Update/Remove), under 72 characters.
Write each paragraph as one continuous line — don't hard-wrap at a column width. gh pr create --body/--body-file sends newlines through verbatim, and GitHub renders each one as a line
break, so a paragraph wrapped at ~100 characters shows up as choppy fragments instead of flowing
text. Only break lines for real markdown structure: blank lines between sections, list items,
headers, code blocks.
Description must include these sections:
## Purpose
[Explain why this change is needed]
## What Changed
- [Key change 1]
## Additional Context
- [Links to issues, tickets, breaking changes]
## Testing
[How to test these changes]