gemini-cli-extensions / gemini-cli-extensions/conductor
newTrack writes spec.md, plan.md, metadata.json and index.md to conductor folder
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.7k
- Forks
- 295
- Avg merge
- 9m
- Merged PRs (30d)
- 1
Description
For some reason newTrack has started writing spec and plan files to the incorrect location. Instead of writing to the conductor/tracks/ folder, :newTrack writes spec.md, plan.md, metadata.json and index.md to conductor folder. This also overwrites the index.md file in the conductor folder. It then detects the issue, and needs to restore index.md from git, and try again. It now does this consistently on every newTrack I add
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.
Research direction
Start by locating the newTrack command and the code that creates the conductor/tracks/ folder. Reproduce the issue with a new track and trace where spec.md, plan.md, metadata.json, and index.md are written. Done means all four files are created only in the track folder and the conductor/index.md file is left unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100