00#792
Conversation
…nt, and ce-plan critic gate - ce-memory-researcher agent + best-effort persistent memory hooks in ce-plan, ce-work, ce-work-beta, ce-debug, ce-compound, ce-commit-push-pr - ce-plan: pre-write critic gate (5.1.7), $ARGUMENTS source-of-truth, 1000-user scalability baseline, plan-critic reference - ce-commit-push-pr: post-ship memory-capture step + reference - ce-work shipping-workflow: read-only review finding gate - claude-to-opencode: generate skill command wrappers when no command owns the skill name - codex-agents: dispatch Task/Agent/Subagent via spawn_agent with parallel-spawn semantics; sequential fallback when unavailable - README: codex local-fork dev guide + stale-flow troubleshooting - Plans + tests for each change
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7db8701778
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| mkdir -p /Users/besi/.codex/plugins/cache/compound-engineering-plugin/compound-engineering/3.4.1 | ||
| cp -R /Users/besi/Code/compound-engineering-plugin/plugins/compound-engineering/. \ | ||
| /Users/besi/.codex/plugins/cache/compound-engineering-plugin/compound-engineering/3.4.1/ |
There was a problem hiding this comment.
Replace the hard-coded Codex cache path
When someone follows this new local-fork workflow, the commands copy skills into /Users/besi/.../3.4.1, but this checkout's Codex plugin manifest is version 3.6.0; on any other machine or after the version changes, Codex will keep reading the active cache path instead of these copied files, so unpublished skill changes still appear stale. Use a placeholder/path variable and derive the cache version from plugins/compound-engineering/.codex-plugin/plugin.json rather than baking in this personal path and old version.
Useful? React with 👍 / 👎.
| @@ -0,0 +1,137 @@ | |||
| --- | |||
| name: ce-memory-researcher | |||
There was a problem hiding this comment.
List ce-memory-researcher in the plugin README
Adding this new agent leaves plugins/compound-engineering/README.md inaccurate: plugins/compound-engineering/AGENTS.md explicitly says, "New agent: Create agents/ce-<name>.agent.md ... Add the agent to the appropriate topical section of README.md ...". Because ce-memory-researcher is now dispatched by several skills but is absent from the Agents table, users browsing the shipped plugin inventory cannot discover this new dependency.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5853657fc3
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| `Use the project-local skill file if it exists: \`.opencode/skills/${skill.name}/SKILL.md\``, | ||
| `Otherwise use the global skill file: \`~/.config/opencode/skills/${skill.name}/SKILL.md\``, |
There was a problem hiding this comment.
Derive the OpenCode skill path from the install root
When OpenCode is installed with a non-default config root, for example OPENCODE_CONFIG_DIR=/custom/opencode, resolveTargetOutputRoot writes the global skills under that configured root and the writer then uses <outputRoot>/skills; this wrapper still tells every generated slash command to read ~/.config/opencode/skills/.... In that environment the new commands are created, but they look in the wrong directory and fail to load the installed skill instructions unless a stale default-root copy happens to exist.
Useful? React with 👍 / 👎.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
No description provided.