Add cross-model review workflow#135
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6cbb3e641c
ℹ️ 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".
|
|
||
| Work from the actual repository state. Keep the change scoped. Before stopping, leave a reviewable artifact: commit, pushed branch, pull request, or a concise .context handoff that names changed files, tests run, and unresolved risks. | ||
|
|
||
| Do not ask TJ to perform a technical step until you have attempted the available local path and documented the exact blocker.`, |
There was a problem hiding this comment.
Remove hard-coded user name from the builder prompt
When anyone other than TJ uses the prompt kit, the copied Builder prompt tells agents not to ask TJ to perform technical steps, which makes the generic Conductor workflow address the wrong person and can confuse handoffs. The same hard-coded name also appears in the reusable cross-model-review skill, so this should use a neutral phrase like “the user” instead.
Useful? React with 👍 / 👎.
Summary
cross-model-reviewskill with builder, reviewer, specialist, and synthesis prompts.Verification
index.htmllocally in Safari.conductor/settings.tomlgit diff --checkCross-Model Review
6cbb3e6.contexthandoff:.context/plans/using-the-conductor-skill-because-this-is-specific.mdRisks
sandboxCwd must be an absolute file URI, so visual proof used Safari plus static responsive checks.