Morrison-Lab
Morrison-Lab/ai-config
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/Morrison-Lab/ai-config --skill r-pkg-news命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| name | r-pkg-news |
| description | Draft NEWS.md changelog entry. |
| user-invocable | true |
| allowed-tools | ["Read","Edit","Write","Bash"] |
Drafts a new NEWS.md entry for an R package, matching the package's
existing entry style and format — as opposed to r-pkg-spellcheck, which
only spellchecks NEWS.md text that's already there and never helps author
it.
Why this exists: most R packages track user-facing changes in
NEWS.md, one entry per release or per notable change, but the exact
format (bullet style, whether entries are grouped under a version heading,
whether they reference issue/PR numbers) varies package to package. Writing
a new entry that doesn't match the existing style creates visible
inconsistency the next release notices.
Confirm this is an R package. Check that DESCRIPTION exists at the
repo root, and that NEWS.md (or NEWS) exists. If either is missing,
skip — this skill doesn't apply, or the package needs to add
NEWS.md first (a one-line file with a version heading and no entries
is enough to start).
Read the existing style. Look at the last 2–3 entries in
NEWS.md and note:
# pkgname 1.2.3) that's
already there for the in-progress version, or need a new one.* , - ), sentence case vs. lowercase lead word,
whether entries end with a period.(#123), (@username)), and where in the sentence that
citation goes.Gather what changed. Pull recent commits since the last tagged
release (git log <last-tag>..HEAD --oneline) or the PR description
supplied by the user, and identify the user-facing changes worth an
entry — skip pure-internal refactors, CI-only changes, and typo fixes
that don't affect behavior unless the project's own style includes
those too (check step 2's precedent).
Draft the entry matching the style read in step 2, one bullet per user-facing change, in plain, direct language (what changed and why it matters to a user — not an internal implementation narrative). Add it under the current in-progress version heading, creating that heading if this is the first entry for the next version.
Spellcheck the new text — hand off to
r-pkg-spellcheck before finishing, since
new NEWS.md prose is exactly the case that skill exists to check before
git push.
r-pkg-spellcheck spellchecks NEWS.md
text against inst/WORDLIST; run it after drafting a new entry here.r-pkg-check and
r-pkg-cran-checklist both expect an
up-to-date NEWS.md entry for the release under check — this skill is
the step that produces it.