- name
Use when writing, restructuring, auditing, or reviewing Cherry Studio repository documentation, READMEs, JSDoc, comments, Agent instructions, or paired English/Chinese docs, including source-linked do
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add CherryHQ/cherry-studio --skill docs-governance -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add CherryHQ/cherry-studio --skill docs-governance -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add CherryHQ/cherry-studio --skill docs-governance -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add CherryHQ/cherry-studio --skill docs-governance -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/CherryHQ/cherry-studio/tree/HEAD/.agents/skills/docs-governanceFrom the publisher
Require an explicit scope. Read the applicable AGENTS.md, then the owning source or module README before judging prose.
docs/dev/references/<domain>/.docs/dev/contrib/.AGENTS.md and link their rationale.Keep one home per fact. A domain README owns its subject and summarizes children with links; it does not copy their implementation detail. A tutorial leads through ordered actions to an observable result. A reference supports lookup and states current behavior.
Run pnpm change:scope --base <verified-ref> and pnpm docs:affected --base <verified-ref>. Inspect every returned document against the changed behavior. A source-prefix match is a mandatory review prompt, not proof that prose needs a diff.
Reference docs describe current reality. Preserve behavior, failure, timing, ownership, modality, exceptions, and consequences. Remove implementation narration, reasoning transcripts, review history, duplicated rationale, status inventories, and catalogs whose source or generator already owns them.
Reference docs carry description and sources; contrib and governance docs carry description. Never hand-edit docs/dev/README.md, docs/dev/sources-index.json, or docs/dev/i18n/terminology.md.
For an in-scope pair, read the pairing contract, translation rules, and terminology. Update the counterpart minimally and re-record only after semantic review. Use translate-docs for new pairs or batch translation.
Documentation-only work runs pnpm docs:check. Script, hook, code-comment, or skill changes also run focused tests, pnpm lint, pnpm test:lint, and git diff --check as applicable.
© 2026 Skills Rack.
---name: docs-governancedescription: Use when writing, restructuring, auditing, or reviewing Cherry Studio repository documentation, READMEs…---# .agents/skills/docs-governance/SKILL.mdOverview
Use when writing, restructuring, auditing, or reviewing Cherry Studio repository documentation, READMEs, JSDoc, comments, Agent instructions, or paired English/Chinese docs, including source-linked documentation impact checks.
FAQ
Download .agents/skills/docs-governance/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/CherryHQ/cherry-studio.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.