菜单
Git operations, branching, commits, PRs, and release workflows. Use when the user asks to "commit", "create PR", "branch", "merge", "rebase", "cherry-pick", "tag", or manage git history.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Testing-grade browser automation via Chrome DevTools Protocol (CDP). Direct access to the browser's DOM, JS runtime, network layer, cookies, computed styles, and console — without any external dependencies. Complements MCP-based tools by enabling arbitrary JS evaluation in page context and deep inspection that screenshot-only tools miss. Use when you need to: run JS in the page, inspect cookies/localStorage, check computed styles, enumerate third-party scripts, emulate devices, analyze network timing, or interact via real mouse and keyboard events.
End-to-end bugfix workflow. Test first, plan, fix, verify. Use when the user says "fix bug", "bugfix", "investigate issue", "fix
Review code for correctness, security, performance, and maintainability. Use when the user asks to "review this code", "check my changes", "review PR", "audit", or "what do you think of this approach".
Gather cross-channel context (local KB, email, Teams chats, optional web) about a person and topic before responding. Use when the user says "what do we know about X", "find prior discussions with Y", "context on this thread", or before drafting any reply where prior history matters.
Disk-first, checkpointed research workflow with three modes — trend research, topic analysis, and fact-checking. Use when the user asks to "research trends", "analyze a topic", "fact-check this", "verify claims", "what's the state of X", or hands you a document to vet.
Goal-backward verification — checks whether the desired outcome was achieved, not whether tasks were marked done. Use when the user asks to "verify", "did this actually work", "is X really done", or before closing an issue / merging a PR.
| name | git-workflow |
| description | Git operations, branching, commits, PRs, and release workflows. Use when the user asks to "commit", "create PR", "branch", "merge", "rebase", "cherry-pick", "tag", or manage git history. |
| license | Apache-2.0 |
| compatibility | Requires git CLI and gh CLI for GitHub operations |
| metadata | {"author":"octobots","version":"0.1.0"} |
Disciplined git operations for professional codebases.
git --no-pager status
git --no-pager log --oneline -5
git --no-pager diff --stat
Always know the current state before changing it.
# Feature branch from main
git checkout main && git pull && git checkout -b feat/short-description
# Bug fix
git checkout main && git pull && git checkout -b fix/issue-description
Branch naming: feat/, fix/, chore/, docs/ prefixes. Lowercase, hyphens, concise.
Never commit unless the user explicitly asks. When they do:
git add -A — avoid secrets and binaries)git add src/auth.py src/middleware.py
git commit -m "$(cat <<'EOF'
Fix session expiry not respecting timezone offset
The previous check used naive datetime comparison which failed
for users in negative UTC offsets.
Co-Authored-By: Claude <noreply@anthropic.com>
EOF
)"
When asked to create a PR:
git --no-pager log main..HEAD --onelinegit --no-pager diff main...HEADgit push -u origin HEADgh pr create --title "Short title under 70 chars" --body "$(cat <<'EOF'
## Summary
- What changed and why (2-3 bullets)
## Test plan
- [ ] How to verify this works
Generated with Claude Code
EOF
)"
Always confirm with the user before:
git push --force (any variant)git reset --hardgit branch -Dgit rebase on shared branchesgit checkout . or git restore . (discards work)Never:
--no-verify)-i) — not supported in non-interactive shellsSee references/recovery.md for common recovery scenarios.