Fix OpenClaw skill markdown import#1040
Conversation
|
CodeAnt AI is reviewing your PR. |
📝 WalkthroughWalkthroughA new OpenClaw/Relaycast skill documentation page is added under ChangesOpenClaw Skill Documentation and Routing
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Suggested labels
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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. Comment |
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
codeant-ai
Bot
added
the
size:XL
|
CodeAnt AI finished reviewing your PR. |
![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: a45130e438
ℹ️ 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".
| Use a shared workspace key (`rk_live_...`) so all claws join the same workspace: | ||
|
|
||
| ```bash | ||
| npx -y @agent-relay/openclaw@latest setup rk_live_SHARED_WORKSPACE_KEY --name my-claw |
There was a problem hiding this comment.
When this markdown is served through /openclaw/skill/invite/:token, applyInviteToken inserts a token-specific setup command but only replaces rk_live_YOUR_WORKSPACE_KEY, so this rk_live_SHARED_WORKSPACE_KEY command remains unchanged directly underneath the invite-specific instructions. Users who copy the join-existing-workspace command from an invite page will register with the literal placeholder instead of the provided workspace key unless this placeholder is also replaced or removed for invite renders.
Useful? React with 👍 / 👎.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
🧹 Nitpick comments (3)
web/content/openclaw/SKILL.md (3)
608-616: ⚡ Quick winAdd language specifier to fenced code block.
For better markdown rendering and syntax highlighting in documentation viewers, specify the language for this code block (use
textfor diagrams).📝 Suggested fix
-``` +```text WS_ACTIVE → (WS failures exceed threshold) → POLL_ACTIVE POLL_ACTIVE → (WS reconnects) → RECOVERING_WS RECOVERING_WS → (WS stable for grace period) → WS_ACTIVE🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@web/content/openclaw/SKILL.md` around lines 608 - 616, The fenced code block containing the state diagram (lines showing WS_ACTIVE → POLL_ACTIVE → RECOVERING_WS → WS_ACTIVE) is missing a language specifier; update the opening fence to include "text" (i.e., ```text) so the diagram is rendered with correct syntax highlighting and markdown rendering in viewers.
406-420: ⚡ Quick winAdd language specifier to fenced code block.
For better markdown rendering and syntax highlighting in documentation viewers, specify the language for this code block.
📝 Suggested fix
-``` +```text [openclaw-ws] Pairing rejected — device is not paired with the OpenClaw gateway. [openclaw-ws] Approve this device: openclaw devices approve 3acae370-6897-41aa-85df-fd9f873f8754 [openclaw-ws] Device ID: 49dacdc54ac11fda...🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@web/content/openclaw/SKILL.md` around lines 406 - 420, The fenced log and command blocks lack a language specifier; update the first fenced block containing the gateway logs (the block that starts with "[openclaw-ws] Pairing rejected — device..." and shows the "openclaw devices approve 3acae370-..." line) to include a language tag such as "text" for the logs, and update the subsequent command fenced block that contains "openclaw devices approve <requestId>" to use "bash" (or "sh") so markdown renderers provide proper syntax highlighting.
432-440: ⚡ Quick winAdd language specifier to fenced code block.
For better markdown rendering and syntax highlighting in documentation viewers, specify the language for this code block.
📝 Suggested fix
-``` +```text [openclaw-ws] Authenticated successfully [gateway] OpenClaw gateway WebSocket client ready🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@web/content/openclaw/SKILL.md` around lines 432 - 440, The fenced code block that shows the OpenClaw logs (lines containing "[openclaw-ws] Authenticated successfully" and "[gateway] OpenClaw gateway WebSocket client ready") should include a language specifier for proper rendering; update that fenced block in SKILL.md to use a language tag (e.g., ```text) immediately after the opening backticks so the code block becomes ```text and retains the same log content.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Nitpick comments:
In `@web/content/openclaw/SKILL.md`:
- Around line 608-616: The fenced code block containing the state diagram (lines
showing WS_ACTIVE → POLL_ACTIVE → RECOVERING_WS → WS_ACTIVE) is missing a
language specifier; update the opening fence to include "text" (i.e., ```text)
so the diagram is rendered with correct syntax highlighting and markdown
rendering in viewers.
- Around line 406-420: The fenced log and command blocks lack a language
specifier; update the first fenced block containing the gateway logs (the block
that starts with "[openclaw-ws] Pairing rejected — device..." and shows the
"openclaw devices approve 3acae370-..." line) to include a language tag such as
"text" for the logs, and update the subsequent command fenced block that
contains "openclaw devices approve <requestId>" to use "bash" (or "sh") so
markdown renderers provide proper syntax highlighting.
- Around line 432-440: The fenced code block that shows the OpenClaw logs (lines
containing "[openclaw-ws] Authenticated successfully" and "[gateway] OpenClaw
gateway WebSocket client ready") should include a language specifier for proper
rendering; update that fenced block in SKILL.md to use a language tag (e.g.,
```text) immediately after the opening backticks so the code block becomes
```text and retains the same log content.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 810be142-fd4e-455d-95e8-497a3ff3a05a
📒 Files selected for processing (3)
web/content/openclaw/SKILL.mdweb/lib/skill-markdown.tsweb/lib/test/skill-markdown.test.ts
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
1 participant
User description
Summary: Move the hosted OpenClaw SKILL.md into web-owned content and update the raw markdown import so the removed packages/openclaw tree is no longer required for the Next build. Verification: npm --prefix web test; npm run build from web.
CodeAnt-AI Description
Move the OpenClaw skill guide into web-owned content and keep it bundled with the app
What Changed
Impact
✅ Fewer broken skill imports during web builds✅ Reliable OpenClaw skill guide delivery✅ Safer app builds after removing the old package path💡 Usage Guide
Checking Your Pull Request
Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.
Talking to CodeAnt AI
Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:
This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.
Example
Preserve Org Learnings with CodeAnt
You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:
This helps CodeAnt AI learn and adapt to your team's coding style and standards.
Example
Retrigger review
Ask CodeAnt AI to review the PR again, by typing:
Check Your Repository Health
To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.