メニュー
Bring the current git branch up to date with commits from the main branch. Use when the user asks to pull latest main, sync/refresh the branch, rebase onto main, or merge main into a feature branch.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Auto-gather git changes, confirm scope with the user, and draft a commit title and message following the project commit style guide.
Extract UX copy and layer names from a Figma frame, page, or component using the Figma MCP server and emit a Markdown table compatible with the project's UX copy workflow. Use when a user provides a Figma URL and asks to pull text into a copy table for review, key naming, or localization.
Lint repository file and folder names for format compliance. Use when users ask to check naming conventions, enforce file extensions, or validate notes naming patterns; applies a fixed set of rules from the skill and reports any discovered repository style guides for reviewer reference.
Polish one or more Markdown files so the repo core writing rules are enforced - straight quotes (not curly), no contractions, the Oxford comma, sentence case headings, plain hyphens (never en-dash or em-dash), consistent capitalization and punctuation, simple non-idiomatic wording, and no sentence split across a line break. After applying these fixes, also runs the link-polisher skill on the same files to format raw URLs. Use when a user asks to polish, clean up, style-check, or enforce writing rules on a Markdown file, or before committing prose changes to docs.
Interact with GitHub repositories using the GitHub CLI (gh). Covers pull requests, issues, releases, workflow runs, and branch operations. Supports beginner and intermediate tracks, write-operation confirmation, and an --auto flag to skip prompts.
Fetch all comments on a GitHub pull request (reviews, inline review comments, and general issue comments) and emit a single consolidated Markdown report. Use when a user wants to read, summarize, audit, or triage every comment on a PR in one place. Accepts a PR number, a `owner/repo#n` reference, or a github.com pull-request URL.
| name | git-pull-main |
| description | Bring the current git branch up to date with commits from the main branch. Use when the user asks to pull latest main, sync/refresh the branch, rebase onto main, or merge main into a feature branch. |
Update the checked out branch from main with a small helper script instead of rebuilding the git sequence from scratch. Prefer rebase for a clean linear history, and switch to merge only when the user or repository workflow requires it.
Confirm the repository state first.
git status --short.git branch --show-current.main.Choose the update strategy.
rebase.merge when the user explicitly asks to merge, the branch is already shared and history should not be rewritten, or the repository conventions prefer merge commits.Run the helper script.
python3 "${CLAUDE_SKILL_DIR}/scripts/update_branch_from_main.py"
Add flags only when needed.
python3 "${CLAUDE_SKILL_DIR}/scripts/update_branch_from_main.py" --strategy merge
python3 "${CLAUDE_SKILL_DIR}/scripts/update_branch_from_main.py" --base-branch main --remote origin
python3 "${CLAUDE_SKILL_DIR}/scripts/update_branch_from_main.py" --allow-dirty
If git reports conflicts, stop normal automation and guide the user through resolution.
git add <files>, then git rebase --continue.git add <files>, then git commit.git rebase --abort or git merge --abort.main.--allow-dirty.origin/main before changing history.origin/main over a stale local main.The helper script:
--allow-dirty is passedorigin/main by default, or merges origin/main when requested