Reframe messaging to self-improving skills, consolidate v0.2.0#24
Reframe messaging to self-improving skills, consolidate v0.2.0#24WellDunDun merged 2 commits intodevfrom
Conversation
Align all consumer-facing surfaces (README, llms.txt, package.json, SKILL.md, AGENTS.md, launch playbook, integration guide) with the "self-improving skills" narrative from the personalization strategy analysis. Consolidate v0.3.0 features into v0.2.0 since dev branch ships everything together. Add Personalization SDK vision to roadmap. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
📝 WalkthroughSummary by CodeRabbit
WalkthroughThis PR reframes project messaging and documentation from "skill observability and continuous improvement" to "self-improving skills," updates v0.2.0 release notes and README feature ordering, expands platform mentions to include OpenClaw, and adds a Personalization SDK entry to the roadmap. Changes are documentation and metadata only. Changes
Sequence Diagram(s)(omitted — changes are documentation/metadata only) Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
package.json (1)
20-35: 🧹 Nitpick | 🔵 TrivialConsider adding "openclaw" to keywords.
Keywords include
claude-code,codex, andopencodebut omitopenclaw— despite OpenClaw being prominently featured as a supported platform throughout the PR (AGENTS.md, integration-guide.md, README.md).Suggested addition
"keywords": [ "selftune", "skill", "self-improving", "claude-code", "codex", "opencode", + "openclaw", "eval", "grading", "evolution",🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@package.json` around lines 20 - 35, Update the package.json "keywords" array to include "openclaw" so the project metadata matches documentation and supported platforms; locate the "keywords" property in package.json and add "openclaw" to the existing list (near entries like "claude-code", "codex", "opencode") ensuring proper JSON syntax and commas.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@CHANGELOG.md`:
- Line 10: The changelog entry header "## [0.2.0] — 2026-03-05" is incorrect for
this PR; either change that header back to an "Unreleased" section (e.g., "##
[Unreleased]") so the notes remain pre-release, or update the date to the
intended ship date "2026-03-17" and keep the "## [0.2.0]" tag—edit the header
line in CHANGELOG.md accordingly to reflect the correct unreleased state or the
real release date.
---
Outside diff comments:
In `@package.json`:
- Around line 20-35: Update the package.json "keywords" array to include
"openclaw" so the project metadata matches documentation and supported
platforms; locate the "keywords" property in package.json and add "openclaw" to
the existing list (near entries like "claude-code", "codex", "opencode")
ensuring proper JSON syntax and commas.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Run ID: 6085f4e3-c0e8-43a3-8aed-e963c1ee0f09
📒 Files selected for processing (9)
AGENTS.mdCHANGELOG.mdREADME.mdROADMAP.mddocs/integration-guide.mddocs/launch-playbook-tracker.mdllms.txtpackage.jsonskill/SKILL.md
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
There was a problem hiding this comment.
♻️ Duplicate comments (1)
CHANGELOG.md (1)
10-10:⚠️ Potential issue | 🟠 MajorKeep
0.2.0underUnreleaseduntil March 17, 2026.This PR was opened on March 8, 2026, so a dated
0.2.0header still makes the changelog read like the release has already shipped. Either keep these notes underUnreleaseduntil the actual cut, or merge this only when the March 17, 2026 release is published.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@CHANGELOG.md` at line 10, The changelog header "## [0.2.0] — 2026-03-17" incorrectly shows a dated release; change that header to keep the 0.2.0 notes under Unreleased until the actual release (e.g., replace the line with "## [Unreleased]" or "## [0.2.0] — Unreleased") so the entry no longer reads as already shipped; ensure the unique header string "## [0.2.0] — 2026-03-17" is updated and leave any associated bullet notes unchanged.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Duplicate comments:
In `@CHANGELOG.md`:
- Line 10: The changelog header "## [0.2.0] — 2026-03-17" incorrectly shows a
dated release; change that header to keep the 0.2.0 notes under Unreleased until
the actual release (e.g., replace the line with "## [Unreleased]" or "## [0.2.0]
— Unreleased") so the entry no longer reads as already shipped; ensure the
unique header string "## [0.2.0] — 2026-03-17" is updated and leave any
associated bullet notes unchanged.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Run ID: 62e93b4a-d67f-4dc0-8fed-61d456e78d26
📒 Files selected for processing (1)
CHANGELOG.md
Summary
What Changed
Ready for March 17 launch with unified messaging.