- name
Use when deciding whether a Cherry Studio change needs an Agent Note, authoring or reviewing a Spec, recording a durable bug-fix decision, moving a note between proposed/implemented/rejected, or check
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 agent-notes -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add CherryHQ/cherry-studio --skill agent-notes -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 agent-notes -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add CherryHQ/cherry-studio --skill agent-notes -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/agent-notesFrom the publisher
Read the Agent Note rules before acting. Agent Notes preserve revisitable decisions; they do not replace current code, reference docs, issues, or PR discussion.
Every human-authored PR declares an Agent Note or an explicit N/A reason. Automation-authored PRs (repository workflows and Dependabot) are exempt from this metadata requirement, not from normal validation.
The class names the decision's subject; it does not force every note to start as proposed. Choose the initial lifecycle from whether the target needs a Spec and whether the decision has already shipped.
N/A for a local or mechanical edit that restores an existing contract without a durable tradeoff.bug-fix note in the same PR when the repair changes failure, compatibility, security, concurrency, atomicity, lifecycle, or another choice likely to be reversed without its root cause.Search by domain terms, mechanism names, paths, and rejected alternatives. Classify the result as new, same owner, partial supersession, or full supersession. Update the existing owner when possible. Partial supersessions stay active and cross-linked. Full supersession must preserve every unique rationale, alternative, consequence, and verification fact; deleting an old note requires explicit human approval.
There is no archived/ lifecycle yet. Do not archive by age, merge status, moved code, or stale wording. Keep current owners factual; keep fully superseded notes active and cross-linked until a separately approved archive design provides active-first search, successor discovery, and matching gates.
AC IDs and a verification owner.gh-create-pr; Spec PR is This PR.gh-stack. Each PR links the Spec and lists its AC coverage.implemented/, rewrites shipped reality in present tense, and maps every AC to actual evidence.Before deciding step 7, run gh stack view --json. If it exits 2, follow the gh-stack skill's remote-discovery procedure; missing local metadata does not prove the PR is standalone. For a stack, inspect the current layer and every downstack implementation PR, then aggregate only ACs backed by verification that was actually run. Intermediate layers keep the note proposed; only the final layer whose cumulative evidence covers every AC in the current Spec performs the transition. Do not infer finality from branch order alone.
After gh stack sync, rerun pnpm change:scope against every live PR base and rerun only checks invalidated by the rewritten scope. A successful sync is not validation.
Only an explicit human decision moves a proposed note to rejected. Discussion, silence, and CHANGES_REQUESTED do not. Preserve a rejected note only when its evidence prevents a plausible repeated mistake; otherwise close the unmerged exploration without adding repository noise. Stop and close any implementation layers after rejection.
For a lifecycle move, run pnpm agent-notes:check-transition --base <verified-spec-ref> in addition to pnpm docs:check-notes, the scoped pairing write/check, pnpm docs:check, and git diff --check. The transition checker validates the declared direction and AC mapping; it never decides rejection or stack completion. Report only evidence actually run.
© 2026 Skills Rack.
---name: agent-notesdescription: Use when deciding whether a Cherry Studio change needs an Agent Note, authoring or reviewing a Spec, recording…---# .agents/skills/agent-notes/SKILL.mdOverview
Use when deciding whether a Cherry Studio change needs an Agent Note, authoring or reviewing a Spec, recording a durable bug-fix decision, moving a note between proposed/implemented/rejected, or checking supersession and stacked Spec approval.
FAQ
Download .agents/skills/agent-notes/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.