Defame1297
14af50bc07
git-workflow's description enumerated the six domains it exists to route away from, so it competed for selection with the very skills it should be handing off to. It now triggers on the case it actually serves: an interactive request whose domain is not yet clear. Also clears frontmatter drift across the plugin and removes duplicated guidance in pc-run that had diverged from its reference.
3.0 KiB
3.0 KiB
name, description, metadata
| name | description | metadata | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| git-workflow | Use when a human's local git request is general or ambiguous — it routes to the owning domain skill. Not an unambiguous commit -> `git-commits`. Not an unambiguous branch -> `git-branches`. Not an agent caller -> `git-orchestrate`. Not Gitea -> `gitea-workflow`. |
|
Gotchas
- Session context built during one multi-step request — branch names, the chosen base, the commit strategy — persists for that request and then clears. Do not re-ask the user for a decision they already gave you earlier in the same workflow.
- Run parent-repo commands through
rtk git <command>, never baregit <command>. This is a mandated org wrapper, not a style preference. Submodule-specific commands run from inside the submodule's own directory instead.
Workflow
- Parse intent — extract the operation (commit, create branch, rebase, inspect history, …) and any options the user named.
- Check the hard rules — if the request creates, amends, or rewrites a commit, pushes, or
touches hooks, config, or credentials, read
references/hard-rules.md. Raise the relevant rule before acting, not after. - Read the repo — current branch, working-tree state, and which branching model the repo
follows (the orchestrator reads
branching_patternfrom plugin config; infer from branch names if absent); the last of those decides which tips are worth offering. - Gate destructive operations — before force-push, branch deletion, rebase, or
force-checkout, show what will happen and ask "Proceed?". Cancel gracefully if the user
declines. Never supply the confirmation on the user's behalf. Some operations are refusals, not
confirmations: never offer "Proceed?" for a force-push of
mainormaster. - Invoke the
git-orchestrateagent withoperation,parameters(user-provided or inferred),context(step 3 plus the session context), andconfirm: trueonly for a destructive op the user approved in step 4. - Clarify when the orchestrator asks for more — put its question to the user in plain language ("Which branch should this be based on?") and loop back to step 5 with the answer.
- Report the outcome — on success, the result and what changed, in plain language; on failure, the error reason and a recovery action.
Interaction style
The caller is a human, so the interaction is the point. Explain each step and why it happens ("I'm squashing your last 3 commits into one clean commit" beats "Squashing commits"), show progress as you go, and prefer natural language to raw command lines.
Match tips to the repo's branching model rather than offering generic advice: on a Gitflow repo,
feature branches come off develop and main tracks only released code; on a trunk-based or
GitHub Flow repo, short-lived branches off main keep merges small and reviewable.