Golem Upgrade
Developmentgolem-upgradeGolem Upgrade is an Agent Skill for development published in the ThinkR-open/golem repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Upgrades the golem Shiny app with the newest golem package features. Triggers on: - "upgrade my Shiny app" - "upgrade app" - "upgrade Shiny app" - "upgrade with newest golem features" - "upgrade to newest golem features" - "update my Shiny app" - "update app" - "update Shiny app" - "update with newest golem features" - "update to newest golem features" Do not trigger on: - if outside an R Shiny app - if outside an R Shiny app which is not golem based
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/ThinkR-open/golem/blob/HEAD/inst/agent-skills/skills/golem-upgrade/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/golem-upgrade, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Main Task
An old golem Shiny app which has been built with an older version of {golem}
gets an upgrade. Upgrade means getting access to newest features, and updates
of meta files and information.
Usage
Use this skill when creating, reviewing, or modifying a golem-based Shiny application, and it is clear that the user wants an upgrade or should get an upgrade from the context of the conversation.
To-Do
IMPORTANT: leave changes likely made by the user as is.
To this end:
I. Make an inventory of the following:
- dev/ folder:
- most often replacing older files with newer versions of the files is enough
- R/app_ui.R & R/app_server.R
- most often replacing older files with newer versions of the files is enough
- R/app_config & R/run_app.R
- sometimes replacing the old file with a newer version is enough, but careful with the possibility of user changes
- inst/golem-config
- could be tricky; make a diff, and only add new fields from new golem version, not changing other fields; still the App may not be that "old" and the user might decide to delete fields on purpose
- old deprecated functions: to find deprecated features refer to
- lookup table under assets/lookup_table.md
- NEWS.md under assets/NEWS.md
II. Compare Shiny app version and golem package version newest golem version
The newest CRAN version is given at
The newest upstream version is given in the master/main branch under
III. Propose to update the R {golem} package (install.packages("golem"))
After the update, migrate functions and metadata to align with the new golem version, BUT AGAIN IMPORTANTLY: do not touch the content likely set by the user: find a way to migrate ! . If unsure what is set by the user, and what comes from an older golem version, ask the user, checkout the older version installed on the system with upstream information at https://github.com/ThinkR-open/golem , evaluate this, and then discuss this with the user.