Menu
Detect user-visible changes from the last 24h of commits on main and propose doc and scenario updates as PRs.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | docs-sync |
| description | Detect user-visible changes from the last 24h of commits on main and propose doc and scenario updates as PRs. |
| version | 0.1.0 |
| license | MIT |
| author | clawrium |
| platforms | ["linux","macos"] |
| metadata | {"cadence":"daily","trigger":"cron","outputs":["pull-request"]} |
Once per day, find code changes that altered user-visible behavior and
propose corresponding updates to docs/ and scenarios/. The goal is
that anyone running the documented commands or following the scenarios
hits the same surface real users hit today.
git log --since='24 hours ago' --first-parent main for the commit
set (first-parent skips merge-squash internals when present).git diff <prev>..<head> per logical change.docs/ and scenarios/.Include a change in scope when any of the following is true:
clawctl CLI
command or option (src/clawrium/cli/).clawctl ps-style status command in a way a user
would notice.Exclude pure refactors, test-only changes, dependency bumps that do not change observable behavior, and internal log strings.
For each cluster of related changes, open one PR titled:
docs(<area>): sync with <one-line behavior change>
PR contents:
docs/ purely for tone or grammar — out of scope.AGENTS.md, CLAUDE.md, or .itx/ from this skill.[draft] in the
title and request input from the author of the originating commit
(one short PR-body line: "@ — please confirm the
user-facing wording").main and waits for
human review.Cut a new clawrium release — bump version, sync docs, tag, trigger PyPI publish
Record a CLI demo (GIF or MP4) using VHS, with storyboard support for long-form / YouTube demos
Watch ric03uec/clawrium release tags; draft a short blog post per user-visible feature as a PR against blog/.
Execute the plan for an issue (parent or subtask)
Know the clawctl CLI and manage your Clawrium fleet (hosts, agents, providers, channels, integrations, skills, secrets)
Check hermes / openclaw / zeroclaw upstream releases and open GitHub issues for each agent that has a newer stable than what the manifest pins