Skip to content
Skills Library
DevOps & cloud · Automation

rootwhy

/rootwhy

Use when a command needs root (sudo, pkexec, doas, su) — installing system packages, editing files in /etc or /usr, restarting system services, changing owners or permissions of system files — or when a direct sudo call was blocked.

Repository
rootwhy ↗
Licence
GPL-3.0
Last repository change
31.10.2026

Assessment and security

96/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content31 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
1
Deprecation

No signals detected. Repository changed on 31.10.2026, without references to retired models or APIs.

Licence

GPL-3.0, otwarta.

What it does and when to use it

Use when a command needs root (sudo, pkexec, doas, su) — installing system packages, editing files in /etc or /usr, restarting system services, changing owners or permissions of system files — or when a direct sudo call was blocked.

Original author description

Use when a command needs root (sudo, pkexec, doas, su) — installing system packages, editing files in /etc or /usr, restarting system services, changing owners or permissions of system files — or when a direct sudo call was blocked.

How it works

SKILL.md has no level-two headings · 26 lines, 281 words

SKILL.md preview
---
name: rootwhy
description: Use when a command needs root (sudo, pkexec, doas, su) — installing system packages, editing files in /etc or /usr, restarting system services, changing owners or permissions of system files — or when a direct sudo call was blocked.
---

# Root commands through rootwhy

Never call `sudo`, `pkexec`, `doas`, `run0` or `su` directly — the user could not see why, and a hook stops it.
Run the command through **rootwhy**: the user gets a dialog with your reason, the command split into coloured parts
and, on hover, what each part does (from the system's man pages), and types the password there. You never see it.

```bash
rootwhy -r "What changes and why, 1–2 sentences in the user's language." -- command args…
```

1. **Check it is installed:** `command -v rootwhy`. If missing, tell the user and point to
   https://github.com/DragonKing026/rootwhy#installation — do not install it yourself, and do not fall back to sudo.
2. **Is root really needed?** Prefer user-level alternatives (`--user` installs, `~/.local`, user systemd units).
3. **Tell the user first** that a password dialog is about to appear, in one sentence.
4. **Reason (`-r`, 10–300 characters)** — the user's language, understandable without this conversation: what will
   change and why, e.g. `Restart Ollama so it picks up the new model directory.` Not a restatement of the command.
5. **One dialog per task:** several steps → one script, `rootwhy -r "…" -- bash /path/to/script.sh`, so the user
   types the password once. Prefer absolute paths; the dialog warns when a script could be changed by someone other
   than root.
6. **Exit codes:** the command's own; `130` = the user cancelled → stop and ask, never retry on your own; `2` = usage
   error (missing reason, no graphical session); `127` = command not found.

`rootwhy --preview -r "…" -- command` shows the dialog without running anything. If the project defines its own
wrapper around rootwhy (e.g. one that logs elsewhere), use the wrapper.

Versions

The database has no other skills named rootwhy.

Database snapshot: 13.11.2026 · package version ee72cc363ea0 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100user-management
    Manage users, groups, and permissions on Linux systems. Configure sudo and access controls. Use when managing system access.
  • 100user-management
    Manage users, groups, and permissions on Linux systems. Configure sudo and access controls. Use when managing system access.
  • 100user-management
    Manage users, groups, and permissions on Linux systems. Configure sudo and access controls. Use when managing system access.
  • 100env
    Install and manage software packages, language runtimes, and CLI tools instantly. Zero barrier — install x-cmd and get any tool in seconds. No sudo required. Use for "install", "package", "python", "node", "jq", "runtime", "tool".
  • 100hogwild
    Operate the Hogwild home server: which SSH host to use, which account holds sudo, what runs there, where each repo, service, route, and config lives, and how to install tools for the Agent. Use for any task that touches Hogwild over SSH.
  • 95rootless-nix
    Install, diagnose, and verify Nix without sudo in Linux cloud or container environments using nix-portable and bubblewrap. Use when /nix is unavailable or unwritable, and when validating a project's nix develop shell.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.