メニュー
Repository contribution workflow. Use for any code change that should become a commit — adding features, fixing bugs, refactoring, or any source modification. Drives the full Issue → Branch → PR → Merge process.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Layout and styling in GPUI. Use when styling components, layout systems, or CSS-like properties.
Performance optimization techniques for GPUI including rendering optimization, layout performance, memory management, and profiling strategies. Use when user needs to optimize GPUI application performance or debug performance issues.
GPUI Component project style guide based on gpui-component code patterns. Use when writing new components, reviewing code, or ensuring consistency with existing gpui-component implementations. Covers component structure, trait implementations, naming conventions, and API patterns observed in the actual codebase.
GPUI styling system including theme design, responsive layouts, visual design patterns, and style composition. Use when user needs help with styling, theming, or visual design in GPUI.
Common GPUI patterns including component composition, state management strategies, event handling, and action dispatching. Use when user needs guidance on GPUI patterns, component design, or state management approaches.
Writing tests for GPUI applications. Use when testing components, async operations, or UI behavior.
| name | contribution-flow |
| description | Repository contribution workflow. Use for any code change that should become a commit — adding features, fixing bugs, refactoring, or any source modification. Drives the full Issue → Branch → PR → Merge process. |
Issue → Branch → PR → Merge workflow for any code change in this repo. Coding standards live in the project's development guidelines (e.g. AGENTS.md); this skill only covers the process.
Shared vocabulary used throughout the flow below: <type> and <scope> placeholders in every step refer back here.
feat | fix | docs | style | refactor | perf | test | build | ci | chore | revertcore, api, ui).<type> must match across the Issue title, branch prefix, every commit, and the PR title. The <scope> is required on commits and the PR title, optional on the Issue title, and omitted from the branch name.Pick the appropriate issue template from .github/ISSUE_TEMPLATE/ — using a template is mandatory. Fill it into /tmp/issue-body.md, then:
gh issue create --title "<type>: ..." --label "<appropriate label>" --body-file /tmp/issue-body.md
Capture the returned number as <N>.
Skipping the Issue: only when the user explicitly asks. Proceed to Step 2 with a descriptive branch name and note the skip in the PR description.
maingit checkout main && git pull --ff-only
git checkout -b <type>/<kebab-slug> # e.g. feat/grid-layout, fix/clipboard-empty-x11
Follow the project's development guidelines.
Must pass before any commit:
./scripts/precheck.sh
git commit -am "<type>(<scope>): <short description>
Refs #<N>"
Multiple commits are fine — they are squashed on merge.
Fill in the PR template from .github/PULL_REQUEST_TEMPLATE.md into /tmp/pr-body.md — using the template is mandatory. Then:
git push -u origin HEAD
gh pr create --base main --title "<type>(<scope>): ..." --body-file /tmp/pr-body.md
Report the PR URL back to the user.
Push additional commits to the same branch. Do not force-push once a reviewer has left feedback, unless the user explicitly requests it.
Only on explicit user instruction.
gh pr merge <N> --squash --delete-branch && \
git checkout main && git pull --ff-only && \
git fetch --prune # Cleanup stale remote-tracking branches
Inspect logs with gh run view --log-failed.