[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7357REGMMK554FK0FZABHQY":3,"skill-same:01M7357REGMMK554FK0FZABHQY":54},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":38,"ownerHtmlUrl":39,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":40,"install":41,"resources":53},"01M7357REGMMK554FK0FZABHQY","r-package-development",null,"R package dev with devtools, testthat, and roxygen2.","Morrison-Lab\u002Fai-config","Morrison-Lab","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F104235520?v=4","01M734G0451S2G35MN4HFQK7XP","Morrison Lab","01M734G059BYFDFQA8YTPDGPMH",4,"MIT","https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fr-package-development\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: r-package-development\ndescription: R package dev with devtools, testthat, and roxygen2.\nuser-invocable: true\nallowed-tools:\n  - Read\n  - Edit\n  - Write\n  - Bash\nmetadata:\n  author: Simon P. Couch (@simonpcouch)\n  version: \"1.2\"\nlicense: MIT\n---\n\n# R package development\n\n## Key commands\n\n```\n# Run code in the package\nRscript -e \"devtools::load_all(); code\"\n\n# Run all tests\nRscript -e \"devtools::test()\"\n\n# Run all tests for files starting with {name}\nRscript -e \"devtools::test(filter = '^{name}')\"\n\n# Run all tests for R\u002F{name}.R\nRscript -e \"devtools::test_active_file('R\u002F{name}.R')\"\n\n# Run a single test \"blah\" for R\u002F{name}.R\nRscript -e \"devtools::test_active_file('R\u002F{name}.R', desc = 'blah')\"\n\n# Redocument the package\nRscript -e \"devtools::document()\"\n\n# Check pkgdown documentation\nRscript -e \"pkgdown::check_pkgdown()\"\n\n# Check the package with R CMD check\nRscript -e \"devtools::check()\"\n\n# Format code\nair format .\n```\n\n## Coding\n\n* Before writing custom helper functions or hand-rolling utilities, research existing functions in base R, tidyverse\u002Fr-lib, ropensci, or existing dependencies per [`prefer-packaged-functions`](..\u002F..\u002Fshared\u002Fcoding\u002Fprefer-packaged-functions.md) and [`prefer-upstream`](..\u002Fprefer-upstream\u002FSKILL.md).\n* Always run `air format .` after generating code.\n* Use the base pipe operator (`|>`) not the magrittr pipe (`%>%`).\n* Use `\\() ...` for single-line anonymous functions.\n  For all other cases, use `function() {...}`.\n\n## Testing\n\nFor the full testthat API (fixtures, mocking, snapshots, BDD-style tests), see [`testing-r-packages`](..\u002Ftesting-r-packages\u002FSKILL.md).\nMatch the package's existing `expect_error()`\u002F`expect_warning()` or snapshot-testing style where precedent exists.\nOn a fresh package with no precedent, follow testing-r-packages' preference for snapshot-based error\u002Fwarning tests.\n\n- Tests for `R\u002F{name}.R` go in `tests\u002Ftestthat\u002Ftest-{name}.R`.\n- All new code should have an accompanying test.\n- If there are existing tests, place new tests next to similar existing tests.\n- Strive to keep tests minimal with few comments.\n- Avoid `expect_true()` and `expect_false()` in favour of a specific expectation which will give a better failure message.\n- When testing errors and warnings, match the package's existing precedent where one exists (see above).\n  On a fresh package with no precedent, use `expect_snapshot(error = TRUE)` for errors and `expect_snapshot()` for warnings, not `expect_error()` or `expect_warning()`.\n  A snapshot lets the user review the full text of the output.\n\n## Documentation\n\n- Every user-facing function should be exported and have roxygen2 documentation.\n- Wrap roxygen comments at 80 characters.\n- Internal functions should not have roxygen documentation.\n- Whenever you add a new (non-internal) documentation topic, also add the topic to `_pkgdown.yml`.\n- Always re-document the package after changing a roxygen2 comment.\n- Use `pkgdown::check_pkgdown()` to check that all topics are included in the reference index.\n\n## `NEWS.md`\n\nThis is the tidyverse-style default.\nWhen the package already has an established `NEWS.md` style, match that existing style instead --- see [`r-pkg-news`](..\u002Fr-pkg-news\u002FSKILL.md), whose whole job is reading a package's precedent before drafting a new entry.\n\n- Every user-facing change should be given a bullet in `NEWS.md`.\n  Do not add bullets for small documentation changes or internal refactorings.\n- Each bullet should briefly describe the change to the end user.\n- If the change is related to a function, put the name of the function early in the bullet.\n- If the bullet is related to a GitHub issue or pull request, reference it by number in parentheses before the final period: `(#123).`.\n- Order bullets alphabetically by function name.\n  Put all bullets that don't mention function names at the beginning.\n\n## Relationship to other skills\n\nThis skill is a day-to-day dev-loop reference (load, test, document, format) with this author's own conventions.\nIt does not replace, and does not cover:\n\n- [`prefer-packaged-functions`](..\u002F..\u002Fshared\u002Fcoding\u002Fprefer-packaged-functions.md) and [`prefer-upstream`](..\u002Fprefer-upstream\u002FSKILL.md) --- researching existing functions and package solutions before hand-rolling custom code.\n- [`r-pkg-check`](..\u002Fr-pkg-check\u002FSKILL.md) --- running and triaging `devtools::check()` output.\n- [`r-pkg-cran-checklist`](..\u002Fr-pkg-cran-checklist\u002FSKILL.md) --- the CRAN release mechanics (win-builder, revdep checks, `devtools::release()`).\n- [`cran-extrachecks`](..\u002Fcran-extrachecks\u002FSKILL.md) --- the ad-hoc\u002Fstylistic CRAN checklist (Title case, `@return` tags, URL hygiene) that `devtools::check()` doesn't catch on its own.\n- [`r-pkg-news`](..\u002Fr-pkg-news\u002FSKILL.md) --- matching a package's existing `NEWS.md` style, which overrides this skill's own default above.\n- [`testing-r-packages`](..\u002Ftesting-r-packages\u002FSKILL.md) --- the full testthat API (fixtures, mocking, snapshots, BDD-style tests).\n  Match the package's existing `expect_error()`\u002F`expect_warning()` or snapshot-testing style where precedent exists.\n  On a fresh package with no precedent, follow testing-r-packages' preference for snapshot-based error\u002Fwarning tests, which agrees with this skill's own default above.\n","# R package development\n\n## Key commands\n\n```\n# Run code in the package\nRscript -e \"devtools::load_all(); code\"\n\n# Run all tests\nRscript -e \"devtools::test()\"\n\n# Run all tests for files starting with {name}\nRscript -e \"devtools::test(filter = '^{name}')\"\n\n# Run all tests for R\u002F{name}.R\nRscript -e \"devtools::test_active_file('R\u002F{name}.R')\"\n\n# Run a single test \"blah\" for R\u002F{name}.R\nRscript -e \"devtools::test_active_file('R\u002F{name}.R', desc = 'blah')\"\n\n# Redocument the package\nRscript -e \"devtools::document()\"\n\n# Check pkgdown documentation\nRscript -e \"pkgdown::check_pkgdown()\"\n\n# Check the package with R CMD check\nRscript -e \"devtools::check()\"\n\n# Format code\nair format .\n```\n\n## Coding\n\n* Before writing custom helper functions or hand-rolling utilities, research existing functions in base R, tidyverse\u002Fr-lib, ropensci, or existing dependencies per [`prefer-packaged-functions`](..\u002F..\u002Fshared\u002Fcoding\u002Fprefer-packaged-functions.md) and [`prefer-upstream`](..\u002Fprefer-upstream\u002FSKILL.md).\n* Always run `air format .` after generating code.\n* Use the base pipe operator (`|>`) not the magrittr pipe (`%>%`).\n* Use `\\() ...` for single-line anonymous functions.\n  For all other cases, use `function() {...}`.\n\n## Testing\n\nFor the full testthat API (fixtures, mocking, snapshots, BDD-style tests), see [`testing-r-packages`](..\u002Ftesting-r-packages\u002FSKILL.md).\nMatch the package's existing `expect_error()`\u002F`expect_warning()` or snapshot-testing style where precedent exists.\nOn a fresh package with no precedent, follow testing-r-packages' preference for snapshot-based error\u002Fwarning tests.\n\n- Tests for `R\u002F{name}.R` go in `tests\u002Ftestthat\u002Ftest-{name}.R`.\n- All new code should have an accompanying test.\n- If there are existing tests, place new tests next to similar existing tests.\n- Strive to keep tests minimal with few comments.\n- Avoid `expect_true()` and `expect_false()` in favour of a specific expectation which will give a better failure message.\n- When testing errors and warnings, match the package's existing precedent where one exists (see above).\n  On a fresh package with no precedent, use `expect_snapshot(error = TRUE)` for errors and `expect_snapshot()` for warnings, not `expect_error()` or `expect_warning()`.\n  A snapshot lets the user review the full text of the output.\n\n## Documentation\n\n- Every user-facing function should be exported and have roxygen2 documentation.\n- Wrap roxygen comments at 80 characters.\n- Internal functions should not have roxygen documentation.\n- Whenever you add a new (non-internal) documentation topic, also add the topic to `_pkgdown.yml`.\n- Always re-document the package after changing a roxygen2 comment.\n- Use `pkgdown::check_pkgdown()` to check that all topics are included in the reference index.\n\n## `NEWS.md`\n\nThis is the tidyverse-style default.\nWhen the package already has an established `NEWS.md` style, match that existing style instead --- see [`r-pkg-news`](..\u002Fr-pkg-news\u002FSKILL.md), whose whole job is reading a package's precedent before drafting a new entry.\n\n- Every user-facing change should be given a bullet in `NEWS.md`.\n  Do not add bullets for small documentation changes or internal refactorings.\n- Each bullet should briefly describe the change to the end user.\n- If the change is related to a function, put the name of the function early in the bullet.\n- If the bullet is related to a GitHub issue or pull request, reference it by number in parentheses before the final period: `(#123).`.\n- Order bullets alphabetically by function name.\n  Put all bullets that don't mention function names at the beginning.\n\n## Relationship to other skills\n\nThis skill is a day-to-day dev-loop reference (load, test, document, format) with this author's own conventions.\nIt does not replace, and does not cover:\n\n- [`prefer-packaged-functions`](..\u002F..\u002Fshared\u002Fcoding\u002Fprefer-packaged-functions.md) and [`prefer-upstream`](..\u002Fprefer-upstream\u002FSKILL.md) --- researching existing functions and package solutions before hand-rolling custom code.\n- [`r-pkg-check`](..\u002Fr-pkg-check\u002FSKILL.md) --- running and triaging `devtools::check()` output.\n- [`r-pkg-cran-checklist`](..\u002Fr-pkg-cran-checklist\u002FSKILL.md) --- the CRAN release mechanics (win-builder, revdep checks, `devtools::release()`).\n- [`cran-extrachecks`](..\u002Fcran-extrachecks\u002FSKILL.md) --- the ad-hoc\u002Fstylistic CRAN checklist (Title case, `@return` tags, URL hygiene) that `devtools::check()` doesn't catch on its own.\n- [`r-pkg-news`](..\u002Fr-pkg-news\u002FSKILL.md) --- matching a package's existing `NEWS.md` style, which overrides this skill's own default above.\n- [`testing-r-packages`](..\u002Ftesting-r-packages\u002FSKILL.md) --- the full testthat API (fixtures, mocking, snapshots, BDD-style tests).\n  Match the package's existing `expect_error()`\u002F`expect_warning()` or snapshot-testing style where precedent exists.\n  On a fresh package with no precedent, follow testing-r-packages' preference for snapshot-based error\u002Fwarning tests, which agrees with this skill's own default above.\n",{"name":5,"license":15,"metadata":24,"description":7,"allowed-tools":27,"user-invocable":32},{"author":25,"version":26},"Simon P. Couch (@simonpcouch)","1.2",[28,29,30,31],"Read","Edit","Write","Bash",true,"main","0f720481f8ce3b3d9fef485f6e230d8b3035748e","skills\u002Fr-package-development",1,"https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config","https:\u002F\u002Fmorrison-lab.github.io\u002Fai-config\u002F","https:\u002F\u002Fgithub.com\u002FMorrison-Lab","2026-11-15 04:39:15",{"source":8,"skillName":5,"commands":42,"prompt":52,"zipAvailable":32},[43,46,49],{"tool":44,"command":45},"npx","npx skills add Morrison-Lab\u002Fai-config --skill r-package-development",{"tool":47,"command":48},"bunx","bunx skills add Morrison-Lab\u002Fai-config --skill r-package-development",{"tool":50,"command":51},"pnpm","pnpm dlx skills add Morrison-Lab\u002Fai-config --skill r-package-development","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fr-package-development\u002FSKILL.md",[],[55,62,69,76,83,90],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M735BVYCGR5VEC65AFDVSNKW","wrap-up","End-of-session verification and UMS.","https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fwrap-up\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M735BTH469T1CQ8G2Q9GENCR","workaround-watcher","Watch upstream issue for fix.","https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fworkaround-watcher\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M735BRKZWFANSQ0GM380B4TD","wn","→ whats-next.","https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fwn\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M735BPE9V830B3B6NGXQ56J6","whats-next","Recommend concrete next step or action.","https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fwhats-next\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M735BMHQ60EAD5B7QAWXC5A0","wait-for-results","Wait for pipeline\u002FCI results.","https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fwait-for-results\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M735BKGZHPN1PEMJ7YBD5VJ8","wai","→ send-notes.","https:\u002F\u002Fgithub.com\u002FMorrison-Lab\u002Fai-config\u002Fblob\u002Fmain\u002Fskills\u002Fwai\u002FSKILL.md",[],[]]