openai / openai/codex-plugin-cc
feat: support jujutsu (jj) workspaces
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 33.3k
- Forks
- 2.3k
- PR merge metrics
- No merged PRs in 30d
Description
I tried to run the /codex:adversarial-review plugin/slash command and it doesn't work from inside a jj workspace.
The Codex plugin calls things like git rev-parse or git diff on the current directory to figure out what to review.
Since my worktree was a jj workspace, not a git worktree and jj has its own .jj/ directory for tracking state instead of .git/, when the Codex script ran git commands there, git didn't recognize it as a repository and failed with something like "This command must run inside a Git repository."
It gave me a manual prompt to paste into Codex directly instead, but I think Claude just made up the prompt, because I don't think it has access to any real Codex prompts (not sure).
Contributor guide
No contributing guide indexed for this repository
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 /codex:adversarial-review plugin and the code that runs git rev-parse or git diff in the current directory. Compare its repository detection with the reported .jj workspace behavior; done means the review command works from a jj workspace without the Git-repository failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100