メニュー
Git operations mastery. Atomic commits, rebase/squash, history search (blame, bisect, log -S). Triggers on 'commit', 'rebase', 'squash', 'who wrote', 'when was X added', 'find the commit that'.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Interview the user relentlessly about a plan or design until branch-level decisions are resolved for execution.
Access Figma designs, extract design systems, and retrieve component specifications. Use when implementing UI from Figma mockups, extracting design tokens, or analyzing design files.
Enforce cost-aware MCP usage. Use when a task might trigger heavy external tools, web search, or broad context expansion. Prevents token burn by ensuring MCPs are only used when local context is insufficient.
Navigate the Warmplane mcp0 facade efficiently. Use when the active config exposes provider capabilities through `mcp0_*` tools and you need to discover or call provider tools without brute-force describing large capability sets. Trigger on requests involving mcp0, Warmplane, or provider work through the facade such as Linear, Notion, Figma, New Relic, Context7, grep.app, or Storybook tools.
Use this when the user needs to control Chrome, navigate to a page, inspect a tab, click or fill elements, take screenshots, or automate a browser flow with aeroxy/chrome-devtools-cli.
Guidelines for creating and managing implementation plans with citations
| name | git-master |
| description | Git operations mastery. Atomic commits, rebase/squash, history search (blame, bisect, log -S). Triggers on 'commit', 'rebase', 'squash', 'who wrote', 'when was X added', 'find the commit that'. |
Each commit should be:
<type>(<scope>): <subject>
<body - optional, explains WHY>
<footer - optional, references issues>
Types: feat, fix, docs, style, refactor, test, chore
# ✅ GOOD
git commit -m "feat(auth): add JWT refresh token support
Enables seamless token refresh without user re-authentication.
Tokens refresh 5 minutes before expiration.
Closes #123"
# ❌ BAD
git commit -m "fixed stuff"
git commit -m "WIP"
git commit -m "update"
git blame <file>
git blame -L 10,20 <file> # lines 10-20 only
git blame -w <file> # ignore whitespace
# Search commit messages
git log --grep="keyword"
# Search code changes (pickaxe)
git log -S "function_name"
git log -S "exact string" --all
# Search with regex
git log -G "pattern.*regex"
git bisect start
git bisect bad HEAD
git bisect good <known-good-commit>
# Git will checkout commits, you test each:
git bisect good # or
git bisect bad
# When done:
git bisect reset
git rebase -i HEAD~3 # last 3 commits
In editor, change pick to:
squash (s) - combine with previous, keep messagefixup (f) - combine with previous, discard messagereword (r) - change commit messageedit (e) - stop to amenddrop (d) - delete commitgit fetch origin
git rebase origin/<base-branch>
# Resolve conflicts if any:
git add <file>
git rebase --continue
Replace <base-branch> with the repository's actual target branch.
| Action | Safety |
|---|---|
git commit | Safe |
git commit --amend | Safe if NOT pushed |
git rebase | Safe if NOT pushed |
git push --force | ⚠️ DESTRUCTIVE - ask first |
git reset --hard | ⚠️ DESTRUCTIVE - ask first |
NEVER force push to main/master without explicit user approval.
git add <files>
git commit --amend --no-edit
# OR to also change message:
git commit --amend -m "new message"
git reset --soft HEAD~1
git stash
git stash pop
git stash list
git stash drop stash@{0}
git checkout -b feature/my-feature
# work, commit...
git push -u origin feature/my-feature
# Ensure up to date
git fetch origin
git rebase origin/<base-branch>
# Push branch
git push -u origin feature/my-feature
# Create PR
gh pr create --title "feat: description" --body "## Summary
- Change 1
- Change 2"
Again, replace <base-branch> with the repository's real PR target branch.