I'm trying to migrate my package-development workflows from the 'do-everything-by-hand' approach to using newer RStudio-style tooling.
One major piece of the puzzle that I'm surprised by is I can't seem to find any function/helper in devtools, usethis, pkgbuild, or related packages that either (i) creates or (ii) suggests the Imports: section of a package's DESCRIPTION. renv already does a great job scanning through R code for dependencies, and @import roxygen2 tag variants would identify any symbols attached within the package, so it seems like this must be doable? When using these RStudio-esque workflows, does a package DESCRIPTION's Import still require by-hand curation during package development?
(Yes, I'm aware of usethis::use_package(...), which I categorize as 'by-hand', since it still requires an explicit action from the developer to add a package to Imports.)