gemini-cli-extensions / gemini-cli-extensions/conductor
[Refactor] Decouple Git from Conductor commands to support multi-VCS (JJ, Piper).
Open
@mahimashanware is already working on this.
Since Jan 16, 2026.
area:revert
feature
p1
- Dominant language
- Python
- Stars
- 3.7k
- Forks
- 295
- Avg merge
- 9m
- Merged PRs (30d)
- 1
Description
Overview
Currently, Conductor commands are tightly coupled to Git. We need to refactor this to support other VCS systems like Jujutsu (JJ) and Piper.
This issue tracks the work to remove Git-specific logic from the core commands and move them into specific workflow templates.
Architecture Changes
1. Workflow Templates
We need to move the default workflow from being hardcoded to Git.
- Current:
templates/workflow.mdis the default. - Plan: Rename the current
templates/workflow.mdto a Git-specific workflow (templates/git_workflow.md) and make the system select the correct workflow based on the user's VCS.
2. Revert Flow
The revert logic in commands/conductor/revert.toml currently assumes Git behavior. We need to:
- Abstract the "revert" concept so it works for various VCS.
- Create separate configuration or strategy patterns for each VCS.
Task List
- Phase 1: Extraction
- Refactor
conductorcommands to remove direct Git dependencies. - Rename
templates/workflow.mdtotemplates/git_workflow.md.
- Refactor
- Phase 2: The Interface
- Implement a mechanism to select the correct workflow file based on the detected VCS.
- Phase 3: New Systems
- Add
templates/jj_workflow.md. - Update
revert.tomllogic to handle non-Git revert flows.
- Add
Related Issues
- Tracks implementation for #52
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.