メニュー
Cherry-pick hotfix commits from production to develop. Use when a hotfix was pushed directly to production and needs to be backported to develop branch.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | cherrypick-hotfix |
| description | Cherry-pick hotfix commits from production to develop. Use when a hotfix was pushed directly to production and needs to be backported to develop branch. |
# Show commits in production that are NOT in develop
git log --oneline develop..production
git checkout develop
git pull origin develop
git cherry-pick <commit-hash>
git push origin develop
# Confirm the commit is now in develop
git branch --contains <commit-hash>
When to cherry-pick to staging:
Default behavior: Only cherry-pick to develop unless user requests staging or context indicates it's needed.
If uncertain: Ask the user: "Should I also cherry-pick this to staging, or is develop sufficient?"
If staging is needed:
git checkout staging
git pull origin staging
git cherry-pick <commit-hash>
git push origin staging
If there are conflicts during cherry-pick:
# Resolve conflicts in the files
# Then continue
git add .
git cherry-pick --continue
# Abort before completing
git cherry-pick --abort
Cherry-pick in chronological order (oldest first):
git cherry-pick <older-commit> <newer-commit>
Work with Pencil .pen design files via the Pencil MCP (batch_design, variables, guidelines). Use when creating or editing .pen files, exploring UI layouts in Pencil, generating wireframes for EduHub, or when the user mentions Pencil, .pen, or the highagency Pencil extension.
Inspect UI via cursor-ide-browser (Cursor Browser tab); fall back to user-playwright if internal browser MCP is unavailable. Use for @Browser, open tab, layout checks, localhost — or when user explicitly asks for Playwright.
Use this skill to generate well-branded interfaces and assets for EduHub by opencampus.sh, either for production or throwaway prototypes/mocks/etc. Contains essential design guidelines, colors, type, fonts, assets, and UI kit components for prototyping.
Draft and review EduHub commit messages using the repository's conventional-commit and semantic-release workflow. Use when writing commit messages, choosing feat vs fix vs chore, deciding whether a body is needed, preparing merge commit messages, or explaining release impact.
Create a GitHub issue on eduhub-org/eduhub and add it to the "EduHub Development" project board with a chosen Status (Backlog / Todo / In Progress / Done). Use when the user asks to "create an issue", "file a ticket", "add to backlog", or otherwise wants a new issue tracked on the project board.
Create and review EduHub Hasura schema migrations. Use when adding tables, columns, constraints, relationships, or other database schema changes, and when coordinating the required metadata, query, type-generation, and function follow-up steps.