القائمة
Git workflow assistant for branching, PRs, and conflict resolution. Use when the user asks about git strategy, branch management, PR workflow, or needs non-interactive git operations.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
First-party, sovereign workflows form — author, list, and validate multi-step workflow specs (YAML, DAG of block/command/agent steps with typed I/O). Use when writing or checking .workflows/*.workflow.yaml. Execution (running workflows) is delivered by SP2; this slice provides the form (workflow_list, workflow_validate).
Conduz um experimento de dogfood onde a colônia Pi executa uma task do .project/tasks.json em dois tempos (research → código) com gates do operador. Use quando o operador quiser ativar um experimento colony-experiment-phase1 ou colony-experiment-phase2.
Use when a Pi session needs to continue local-safe work with low operator friction: discover focus, interview only for missing constraints, prepare bounded slices, use workers only behind gates, checkpoint, and stop on real risk.
Interact with web pages via browser automation: navigate, click, fill forms, screenshot, and evaluate JavaScript. Uses Chrome/Chromium remote debugging (CDP).
Operar o control-plane local-first do agents-lab com board canônico, long-runs bounded, handoff/checkpoint, rollout/rollback e espelhos externos sem perder governança.
Guia o cultivo de uma primitiva reutilizável. Use quando o usuário identificar um padrão recorrente que merece ser extraído como skill, extensão ou convenção.
| name | git-workflow |
| description | Git workflow assistant for branching, PRs, and conflict resolution. Use when the user asks about git strategy, branch management, PR workflow, or needs non-interactive git operations. |
Help with Git operations and workflow strategy.
# Inspect current state
git branch -a
git log --oneline -20
git status
Recommend strategy based on project context:
main + short-lived feature branchesmain + develop + feature/* / fix/* branchesmain / develop / release/* / hotfix/*)git diff main --stat — review what changedgit log --format='%an' -- <files>PR: https://github.com/owner/repo/pull/42
gh pr view --json url --jq .url (GitHub) or glab mr view --output json | jq .web_url (GitLab)git diff --name-only --diff-filter=U — find conflicted filesGuide through git rebase -i for cleaning history before a PR.
If resolving conflicts during rebase, continue non-interactively:
GIT_EDITOR=true git rebase --continue
When the agent runs git or gh/glab, never open an interactive editor or prompt.
Commits — always pass message on the command line:
git commit -m "fix(scope): message"
Rebase continue — --no-edit is not supported, use:
GIT_EDITOR=true git rebase --continue
# or
git -c core.editor=true rebase --continue
Merge — reuse existing message:
git merge --no-edit
Any other git command that could open an editor:
GIT_EDITOR=true git <command>
GitHub CLI — disable prompts and provide all fields explicitly:
GH_PROMPT_DISABLED=1 gh pr create --title "..." --body "..."
GH_PROMPT_DISABLED=1 gh pr merge --squash --delete-branch
GitLab CLI — same principle:
glab mr create --title "..." --description "..." --yes
glab mr merge --yes
Only allow interactive editors or prompts when the user explicitly asks for them.