rtunk linters lists the linters available to your repository and adds them to or removes them from the configuration; rtunk config print shows what the configuration resolves to.

rtunk linters enable shellcheck

rtunk linters list groups linters as enabled, available for this repository, and (with --all) the rest. A linter counts as available when its suggest_if says so: by default (files_present, or unset) when it matches at least one file in the repository, with config_present when one of its direct_configs exists, never with never. Groups are separated by a blank line.

$ rtunk linters list
Available for this repo (not enabled)
  ◯ checkov         1 file
  ◯ git-diff-check  4 files
  ◯ markdownlint    1 markdown file
  ◯ prettier        2 files
  ◯ shellcheck      1 shell file
  ◯ shfmt           1 shell file
  ◯ trufflehog      4 files
  ◯ yamllint        1 yaml file
(121 other linters — rtunk linters list --all)

Enable one with: rtunk linters enable <id>

Pass --all to show the remaining linters as a third group, Other (linters matching no file, and linters matching files that suggest_if does not suggest), or --format json for machine-readable output (enabled, available and other arrays with id, version, files and description).

On a terminal, group headers are bold, enabled marks are green and linters matching no file are dimmed; piped output, or any output with NO_COLOR set, is plain text. The collapsed hint reads (1 other linter — ...) for a single linter.

Pass one or more ids. Append @<version> to pin a version.

$ rtunk linters enable shellcheck [email protected]
$ rtunk linters list
Enabled
  ✔ shellcheck      1 shell file
  ✔ [email protected]     1 shell file
Available for this repo (not enabled)
  ◯ checkov         1 file
  ...

The command edits lint.enabled in .rtunk/rtunk.yaml:

lint:
  enabled:
    - shellcheck
    - [email protected]

Either way, the command then prints what changed and how to fetch the tools:

$ rtunk linters enable shellcheck [email protected]
Enabled: shellcheck, shfmt

Download them now with:
  rtunk download lint shellcheck shfmt

Disabled: <ids> is printed when the picker unchecks enabled linters; the download hint appears only if something was enabled. Downloading is optional: check, fmt and run download lazily.

Without ids, rtunk linters enable opens a full-screen interactive picker (alternate screen, the terminal is restored on exit) over the same groups as linters list --all, separated by blank lines. The list scrolls to the terminal height and follows resizes; ↓ N more counts the items below the viewport. Typing filters on the id (backspace edits; a filter: line shows (visible/total)), up/down move, space toggles, enter confirms, esc or ctrl-c cancels. q does not cancel: it is typed into the filter. Linters matching no file are dimmed. The picker needs a terminal; without one the command stops with interactive mode requires a terminal; pass explicit id(s) instead.

rtunk linters disable shfmt

This removes the linter from the configuration. Disabled linters no longer run in rtunk check or rtunk fmt.

enable and disable edit only the base config file. To switch a linter off for yourself, or one that a local override file enables, list it under lint.disabled in .rtunk/rtunk.local.yaml; it then stays off whichever file enables it. enable and disable warn on stderr when an override decides otherwise (warning: <id> stays disabled: <file> lists it under lint.disabled, warning: <id> stays enabled: <file> enables it ...), and linters list marks such linters with (from <file>) or (disabled by <file>).

Two commands print YAML (or JSON with --output json):

$ rtunk config print
version: "0.1"
cli:
    version: ""
plugins:
    sources:
        trunk:
            id: trunk
            uri: https://github.com/trunk-io/plugins
            ref: v1.11.0
...
lint:
    enabled:
        - shellcheck

The output is long (the trunk plugin source alone defines about 130 linters); pipe it to a pager or grep. Use it to see which commands, files and tools a linter will actually use.

• Checking code — run the linters you enabled
• Command Reference — every flag of the linters commands
• Configuration Reference — the lint keys in rtunk.yaml