菜单
Git workflow assistant for branching, commits, PRs, and conflict resolution. Use when user asks about git strategy, branch management, or PR workflow.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Write commit messages that capture judgment and decision-making, not just change descriptions. Use when the user wants to elevate their commit history from a log to a record of reasoning, trade-offs, and context.
Debug assistant for error analysis, log interpretation, and performance profiling. Use when user encounters errors, crashes, or performance issues.
Detect project type and generate .pi/ configuration. Use when setting up pi for a new project or when user asks to initialize pi config.
Fetch a web page and extract readable text content. Use when user needs to retrieve or read a web page.
Web search via DuckDuckGo. Use when the user needs to look up current information online.
Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports.
| name | git-workflow |
| description | Git workflow assistant for branching, commits, PRs, and conflict resolution. Use when user asks about git strategy, branch management, or PR workflow. |
Help with Git operations and workflow best practices.
# Check current state
git branch -a
git log --oneline -20
git status
Recommend branching strategy based on project:
Follow Conventional Commits:
feat(scope): add new feature
fix(scope): fix bug description
refactor(scope): restructure code
docs(scope): update documentation
test(scope): add/update tests
chore(scope): maintenance tasks
git diff main --stat — Review changesgit log --format='%an' -- <files>)When a PR has been opened, always include the full GitHub PR URL in any summary or status update you provide. This makes it easy for the user to click through to the PR directly.
Example summary format:
PR: https://github.com/owner/repo/pull/42
Use gh pr view --json url --jq .url to retrieve the URL if you do not already have it.
When the agent runs git or gh, avoid opening an interactive editor or prompt.
A lot of Git entrypoints use different editor config keys, so avoid surprises by disabling both:
core.editor / GIT_EDITOR (commit, merge, tag message editing)sequence.editor / GIT_SEQUENCE_EDITOR (interactive rebase todo-list editing)Use this pattern for non-interactive flows:
GIT_EDITOR=true GIT_SEQUENCE_EDITOR=true git -c core.editor=true -c sequence.editor=true rebase --continue
git commit -m "fix(scope): message"
git merge --no-edit
GIT_EDITOR=true and GIT_SEQUENCE_EDITOR=true (plus -c core.editor=true -c sequence.editor=true) for that invocation.GH_PROMPT_DISABLED=1 gh pr create --title "..." --body "..."
GH_PROMPT_DISABLED=1 gh pr merge --squash --delete-branch
git diff --name-only --diff-filter=U — Find conflicted filesGuide through git rebase -i for cleaning up history before PR.
If the agent is resolving conflicts during a rebase, continue with a non-interactive command such as:
GIT_EDITOR=true GIT_SEQUENCE_EDITOR=true git -c core.editor=true -c sequence.editor=true rebase --continue