Keep direct lintr usage

Co-authored-by: Bryce Mecum <[email protected]>

Author: kou

r/vignettes/developers/workflow.Rmd

@@ -51,7 +51,7 @@ pkgdown::build_site(preview=TRUE)
 
 ## Styling and linting
 
-You can automatically adjust our styling and lint by [pre-commit](https://pre-commit.com/):
+Styling and linting can be set up and performed entirely with the [pre-commit](https://pre-commit.com/) tool:
 
 ```bash
 pre-commit run --show-diff-on-failure --color=always --all-files r
@@ -67,6 +67,15 @@ You can automatically change the formatting of the code in the package using the
 
 The styler package will fix many styling errors, thought not all lintr errors are automatically fixable with styler. The list of files we intentionally do not style is in `r/.styler_excludes.R`.
 
+Linting and styling with [pre-commit](https://pre-commit.com/) as described above is the best way to ensure your changes are being checked properly but you can also run the tools individually if you prefer:
+
+```r
+lintr::lint_package() # for linting
+styler::style_pkg() # for styling
+```
+
+Note: To run lintr, we require the `cyclocomp` package to be installed first.
+
 ### C++ code
 
 The arrow package uses some customized tools on top of [cpp11](https://cpp11.r-lib.org/) to prepare its