Skip to content

Add and update requested tools according to the workflow#68

Open
popemkt wants to merge 2 commits intomainfrom
add-new-items-14952204770370296087
Open

Add and update requested tools according to the workflow#68
popemkt wants to merge 2 commits intomainfrom
add-new-items-14952204770370296087

Conversation

@popemkt
Copy link
Copy Markdown
Owner

@popemkt popemkt commented Mar 12, 2026

Created manifests for cli-anything and sem as remote repos. Updated the codex-cli manifest to include the 'Reference' tag. Verified that jean and jules are already present and correctly configured.


PR created automatically by Jules for task 14952204770370296087 started by @popemkt


Open with Devin

Summary by CodeRabbit

  • New Features
    • Added CLI-Anything app integration for remote repository management with clone and documentation commands.
    • Added Sem project integration as a development tool with installation and documentation commands.
    • Updated Codex CLI metadata with Reference tags for improved organization.

Created manifests for cli-anything and sem as remote repos.
Updated the codex-cli manifest to include the 'Reference' tag.
Verified that jean and jules are already present and correctly configured.

Co-authored-by: popemkt <35656480+popemkt@users.noreply.github.com>
@google-labs-jules
Copy link
Copy Markdown
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Mar 12, 2026

📝 Walkthrough

Walkthrough

Three app manifest configurations are introduced or updated for the Nxus platform: CLI-Anything and Sem are newly added with complete manifest definitions (commands, dependencies, installation configs), while Codex-CLI's existing manifest is updated with a reference tag.

Changes

Cohort / File(s) Summary
New App Manifests
apps/nxus-core/src/data/apps/cli-anything/manifest.json, apps/nxus-core/src/data/apps/sem/manifest.json
Added complete manifest configurations for CLI-Anything and Sem remote repository apps, each defining commands (clone, docs/GitHub), dependencies, metadata tags, categories, timestamps, version, author, and multi-platform installation configurations (pip/Cargo).
Codex-CLI Manifest Update
apps/nxus-core/src/data/apps/codex-cli/manifest.json
Updated metadata.tags from empty array to include a "Reference" tag object with id and name fields.

Estimated Code Review Effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Poem

🐰 A rabbit discovers three treasures so fine,
New manifests shining in structured design,
CLI-Anything and Sem join the fold,
With commands and configs, a story untold,
Tags and dependencies perfectly aligned! ✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately summarizes the main changes: adding new tool manifests (cli-anything and sem) and updating an existing tool manifest (codex-cli) as part of a workflow.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch add-new-items-14952204770370296087

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown

@devin-ai-integration devin-ai-integration bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 4 additional findings.

Open in Devin Review

Copy link
Copy Markdown

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@apps/nxus-core/src/data/apps/cli-anything/manifest.json`:
- Around line 39-42: The root-level "installConfig" entry in manifest.json
incorrectly runs `pip install -e .` at the repository root; remove the entire
"installConfig" object from
apps/nxus-core/src/data/apps/cli-anything/manifest.json so the manifest no
longer executes an installation in the wrong location, or if this was intended
for generated apps instead, move or re-add an installConfig into the generated
app’s manifest with the script updated to change into the agent-harness
directory (e.g., `cd agent-harness && pip install -e .`) so the install runs in
the correct subdirectory.

In `@apps/nxus-core/src/data/apps/codex-cli/manifest.json`:
- Around line 39-45: Update the manifest's metadata.updatedAt timestamp to the
current ISO 8601 time so the file reflects the recent change; specifically edit
manifest.json's "metadata" block (the "updatedAt" field next to "createdAt") and
set it to the new current timestamp, ensuring the format matches the existing
ISO 8601 string.

In `@apps/nxus-core/src/data/apps/sem/manifest.json`:
- Around line 30-43: Update the manifest so the install command matches Sem's
README: change installConfig.script to navigate into the crates directory and
run cargo install --path sem-cli (e.g., "cd crates && cargo install --path
sem-cli"), and add "cargo" to the top-level dependencies array so the required
tool is declared; modify the installConfig.script and dependencies entries in
the manifest.json accordingly.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 5fc9a162-c56e-4774-bef6-02db80cc0199

📥 Commits

Reviewing files that changed from the base of the PR and between 7ddc19b and c5f7a92.

📒 Files selected for processing (3)
  • apps/nxus-core/src/data/apps/cli-anything/manifest.json
  • apps/nxus-core/src/data/apps/codex-cli/manifest.json
  • apps/nxus-core/src/data/apps/sem/manifest.json

Comment on lines +39 to +42
"installConfig": {
"script": "pip install -e .",
"platform": ["linux", "macos", "windows"]
}
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

# First, examine the manifest.json file to understand context
cat -n apps/nxus-core/src/data/apps/cli-anything/manifest.json

Repository: popemkt/nxus

Length of output: 1769


🏁 Script executed:

# Search for any CLI-Anything related documentation or references in the repo
rg -i "cli-anything" --type json --type md -A 3 -B 3

Repository: popemkt/nxus

Length of output: 2808


🏁 Script executed:

# Check for other manifest files to see if there's a pattern
find apps/nxus-core/src/data/apps -name "manifest.json" -type f

Repository: popemkt/nxus

Length of output: 3708


🌐 Web query:

CLI-Anything installation documentation github.com/HKUDS/CLI-Anything README setup

💡 Result:

CLI-Anything (HKUDS/CLI-Anything) — README setup / installation

Prerequisites

  • Python 3.10+
  • The target software installed (e.g., GIMP/Blender/LibreOffice)
  • A supported AI coding agent (e.g., Claude Code or OpenCode) [1]

Install (Claude Code)

/plugin marketplace add HKUDS/CLI-Anything
/plugin install cli-anything

Then run (example):

/cli-anything:cli-anything ./gimp

(If Claude Code is under 2.x, use /cli-anything instead.) [1]

Manual install (Claude Code plugin):

git clone https://github.com/HKUDS/CLI-Anything.git
cp -r CLI-Anything/cli-anything-plugin ~/.claude/plugins/cli-anything

Then in Claude Code:

/reload-plugins

[2]

Install (OpenCode)

git clone https://github.com/HKUDS/CLI-Anything.git

# Global install
cp CLI-Anything/opencode-commands/*.md ~/.config/opencode/commands/
cp CLI-Anything/cli-anything-plugin/HARNESS.md ~/.config/opencode/commands/

# Or project-level install
cp CLI-Anything/opencode-commands/*.md .opencode/commands/
cp CLI-Anything/cli-anything-plugin/HARNESS.md .opencode/commands/

This adds slash commands like /cli-anything, /cli-anything-refine, /cli-anything-test, /cli-anything-validate, /cli-anything-list. [2]

Use the generated CLI (after generation)

Example from the README:

cd gimp/agent-harness && pip install -e .
cli-anything-gimp --help

[1]

Sources: GitHub README for HKUDS/CLI-Anything. [1][2]


Remove installConfig — it references incorrect installation step for this remote repo.

CLI-Anything's documented setup involves cloning the repo, copying plugin files, generating a CLI wrapper, and then running pip install -e . from within the generated app's agent-harness directory. The manifest's root-level installConfig does not match this flow and would execute at the wrong location. Either remove this config or document the correct subdirectory path if intended for generated app scenarios. (github.com/HKUDS/CLI-Anything)

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@apps/nxus-core/src/data/apps/cli-anything/manifest.json` around lines 39 -
42, The root-level "installConfig" entry in manifest.json incorrectly runs `pip
install -e .` at the repository root; remove the entire "installConfig" object
from apps/nxus-core/src/data/apps/cli-anything/manifest.json so the manifest no
longer executes an installation in the wrong location, or if this was intended
for generated apps instead, move or re-add an installConfig into the generated
app’s manifest with the script updated to change into the agent-harness
directory (e.g., `cd agent-harness && pip install -e .`) so the install runs in
the correct subdirectory.

Comment on lines 39 to 45
"metadata": {
"tags": [],
"tags": [
{ "id": "reference", "name": "Reference" }
],
"category": "development-tools",
"createdAt": "2026-02-25T14:00:00Z",
"updatedAt": "2026-02-25T14:00:00Z",
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Refresh metadata.updatedAt when changing the manifest.

Line 45 still reports the old timestamp even though this PR modifies the metadata block. That leaves the manifest with stale freshness data.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@apps/nxus-core/src/data/apps/codex-cli/manifest.json` around lines 39 - 45,
Update the manifest's metadata.updatedAt timestamp to the current ISO 8601 time
so the file reflects the recent change; specifically edit manifest.json's
"metadata" block (the "updatedAt" field next to "createdAt") and set it to the
new current timestamp, ensuring the format matches the existing ISO 8601 string.

Comment on lines +30 to +43
"dependencies": ["git"],
"metadata": {
"tags": [
{ "id": "useful", "name": "Useful" }
],
"category": "development-tools",
"createdAt": "2026-03-12T00:00:00Z",
"updatedAt": "2026-03-12T00:00:00Z",
"version": "1.0.0",
"author": "Ataraxy-Labs"
},
"installConfig": {
"script": "cargo install --path .",
"platform": ["linux", "macos", "windows"]
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

# First, check if the manifest file exists and read its content
cat -n apps/nxus-core/src/data/apps/sem/manifest.json

Repository: popemkt/nxus

Length of output: 1819


🌐 Web query:

Sem CLI installation requirements Ataraxy-Labs repository

💡 Result:

Sem CLI (Ataraxy-Labs/sem) installation requirements (by install method)

  • Build from source / install via Cargo: requires the Rust toolchain (Cargo), plus Git to clone the repo. (github.com)
  • Prebuilt binary (GitHub Releases): no build tools required—download a release binary appropriate for your OS/arch. (github.com)
  • Docker-based install/run: requires Docker (build image + run container). (github.com)
  • Homebrew install (macOS/Linux): requires Homebrew (brew install ataraxy-labs/tap/sem). (ataraxy-labs.github.io)

Citations:


🌐 Web query:

Sem Ataraxy-Labs repository structure crates/sem-cli cargo install README

💡 Result:

  • Repository layout (high level): the Ataraxy-Labs/sem repo contains a Rust Cargo workspace under crates/ plus other top-level folders like src/, docs/, site/, etc. (github.com)
  • Workspace crates: crates/ includes (at least) two crates:
    • crates/sem-core/ (library)
    • crates/sem-cli/ (binary CLI) (github.com)
  • crates/sem-cli structure: the CLI crate directory contains src/ and its Cargo.toml. (github.com)

Install (sem-cli) per README/docs

  • Direct from git (no clone):
    cargo install --git https://github.com/Ataraxy-Labs/sem sem-cli
    (ataraxy-labs.github.io)
  • From a local clone (path install):
    git clone https://github.com/Ataraxy-Labs/sem
    cd sem/crates
    cargo install --path sem-cli
    (github.com)

Citations:


🏁 Script executed:

# Search for any documentation or README files that might clarify the install path
curl -s https://raw.githubusercontent.com/Ataraxy-Labs/sem/main/README.md | head -100

Repository: popemkt/nxus

Length of output: 2655


installConfig.script and missing Cargo dependency.

The manifest runs cargo install --path ., but Sem's source install (documented in the README) requires navigating to crates/ and running cargo install --path sem-cli. The command targets the wrong directory, and the manifest also omits cargo from dependencies despite being a required tool for the install script.

Suggested manifest fix
-    "dependencies": ["git"],
+    "dependencies": ["git", "cargo"],
...
     "installConfig": {
-        "script": "cargo install --path .",
+        "script": "cargo install --path crates/sem-cli",
         "platform": ["linux", "macos", "windows"]
     }
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
"dependencies": ["git"],
"metadata": {
"tags": [
{ "id": "useful", "name": "Useful" }
],
"category": "development-tools",
"createdAt": "2026-03-12T00:00:00Z",
"updatedAt": "2026-03-12T00:00:00Z",
"version": "1.0.0",
"author": "Ataraxy-Labs"
},
"installConfig": {
"script": "cargo install --path .",
"platform": ["linux", "macos", "windows"]
"dependencies": ["git", "cargo"],
"metadata": {
"tags": [
{ "id": "useful", "name": "Useful" }
],
"category": "development-tools",
"createdAt": "2026-03-12T00:00:00Z",
"updatedAt": "2026-03-12T00:00:00Z",
"version": "1.0.0",
"author": "Ataraxy-Labs"
},
"installConfig": {
"script": "cargo install --path crates/sem-cli",
"platform": ["linux", "macos", "windows"]
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@apps/nxus-core/src/data/apps/sem/manifest.json` around lines 30 - 43, Update
the manifest so the install command matches Sem's README: change
installConfig.script to navigate into the crates directory and run cargo install
--path sem-cli (e.g., "cd crates && cargo install --path sem-cli"), and add
"cargo" to the top-level dependencies array so the required tool is declared;
modify the installConfig.script and dependencies entries in the manifest.json
accordingly.

Created manifests for cli-anything and sem as remote repos.
Updated the codex-cli manifest to include the 'Reference' tag.
Verified that jean and jules are already present and correctly configured.

Co-authored-by: popemkt <35656480+popemkt@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant