Repository navigation
Say how to use the plugin: one claude --worktree session per task - #4
Conversation
The README gains a Use section and points at the marketplace for the install commands. The session-start rules and the skill name the same command, so an agent in the main checkout can tell the human how to start a task. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Vtrv52oTpCLDMKzN13i4Nw
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6f0bf998ce
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| Start each analysis task as its own session, from the analysis repo's main checkout: | ||
|
|
||
| ```bash | ||
| claude plugin marketplace add quadbio/claude-plugins | ||
| claude plugin install analysis-workflow@quadbio | ||
| claude --worktree <task> |
There was a problem hiding this comment.
When the local main checkout is behind or ahead of origin, launching this command from it does not ensure that the task uses that checkout's revision: Claude Code's default fresh mode will “branch from your repository’s default branch on the remote”. The task can therefore contain a newer pixi.toml while the workflow executes it using the stale main checkout environment, or it can omit unpushed setup changes. Require a clean, up-to-date main checkout before this command (or explicitly configure worktree.baseRef: "head") so the task code and shared environment stay aligned.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Fixed in cc5fac0: the Use section now says to pull the main checkout first, since the worktree branches from origin's default branch but runs on the main checkout's environment. Not switching to worktree.baseRef: "head": starting from the merged default branch is what we want; the stale main checkout is the thing to fix.
claude --worktree branches from origin's default branch, while the task runs on the main checkout's environment; a stale main checkout pairs new code with an old environment. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Vtrv52oTpCLDMKzN13i4Nw
1 participant
Usesection (start each task withclaude --worktree <task>from the main checkout; what happens; what stays with the human).Installpoints at the quadbio marketplace, the one place the commands live.Merging this, then tagging
v0.2.0, completes the release that #3 started.🤖 Generated with Claude Code
https://claude.ai/code/session_01Vtrv52oTpCLDMKzN13i4Nw