[darko-mijic]

Relay 2.2.3 is a documentation release on the 2.x line, which takes bug fixes only.

What changes

The relay:jobs skill documented steering only in a table near its end, after the backend reference. Agents using relay often did not know a running job could be steered, and the skill's description, which Claude sees before it loads a skill, did not mention it.

• The description now says that SendMessage to a job's agent joins the running turn (on Kimi, the next turn), continues the same session after the job ends, and that the message cancel cancels it. It is 431 characters, under Claude Code's per-skill listing cap of 1,536.
• The skill's first lines, right under the launch snippet, say the same and add: to change a job's direction, message it rather than stopping it and starting another. They link to the existing table, which stays the full reference.

No code changes. Version fields move to 2.2.3 together.

Verification

• tests/commands.test.mjs (19) and tests/zcode.test.mjs (40), the suites that read the skill, pass.
• npm run check, npm run check-version and git diff --check pass.
• claude plugin validate passes for the plugin and the marketplace manifest.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Clarified how to steer a running job by sending a message, including that messages join the active turn or queue for the next turn on Kimi.
  • Explained that a job’s session can continue after the job ends, and that cancel stops the job.
  • Updated the release information to reflect these job-steering details and the 2.2.3 version.

Confidence Score: 5/5

This documentation release appears safe to merge.

Summary

This documentation release makes job steering visible before Claude loads the skill and immediately after the launch example.

• The jobs skill now explains how to steer and continue a running job.

No actionable issues found. Message routing and release fields were checked against the code; tests were not run during this review.

_{Reviews (1) · Last reviewed commit: "relay 2.2.3: the jobs skill says up fron..." · Reviewed by Greptile}

[coderabbitai]

No actionable comments were generated in the recent review.

Walkthrough

The relay:jobs skill now explains how SendMessage steers running and completed jobs, including Kimi’s next-turn behavior and job cancellation. Release metadata and the changelog were updated to version 2.2.3.

Changes: Jobs steering guidance

Layer / File(s)	Summary
Jobs guidance and release metadata plugins/relay/skills/jobs/SKILL.md, plugins/relay/CHANGELOG.md, .claude-plugin/marketplace.json, plugins/relay/.claude-plugin/plugin.json, package.json	The skill describes SendMessage behavior during and after jobs, Kimi’s next-turn handling, and cancellation. The changelog records the guidance, and the package and plugin versions change to 2.2.3.

Estimated code review effort: 2 (Simple) | ~8 minutes

Change: Other

Possibly related PRs

• libar-dev/relay-plugin-cc#60: Changes job message delivery and cancellation behavior that the documented controls use.
• libar-dev/relay-plugin-cc#32: Documents SendMessage steering and session continuation for Agent-tool relay sessions.

Merge Risk: Minimal · up to efdfc

This documentation release clarifies job steering without changing runtime code. No merge-blocking issue is identified in the supplied changes.

Pre-merge checks: 5

Check name	Status	Explanation
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Title check		The title clearly and concisely describes the main change: documenting up front that a running Relay job can be steered.
Docstring Coverage		No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (5 skipped: 5 unsupported.)

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

• X
• Mastodon
• Reddit
• LinkedIn

CodeRabbit Verify

• Run CodeRabbit Verify to test the changes in this pull request.

Recent review info

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Repository UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: 3572fe6c-67a4-4dad-ac79-ebe7f85a6afc

Commits

Reviewing files that changed from the base of the PR and between 8cca168 and efdfc82.

Files ignored due to path filters: 1

• package-lock.json is excluded by !**/package-lock.json

Files selected for processing: 5

• .claude-plugin/marketplace.json
• package.json
• plugins/relay/.claude-plugin/plugin.json
• plugins/relay/CHANGELOG.md
• plugins/relay/skills/jobs/SKILL.md

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.