Menú
Use pkexec first for commands that need root directly or indirectly.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Execute broad changes one coherent, independently verifiable stage at a time. Use when work spans multiple independently reviewable changes, or when contracts, producer-consumer migrations, generated artefacts, or release packaging create an ordered multi-stage rollout; skip small single-purpose changes.
Commit workflow using the dot git-commit gateway in the maintainer's concise one-line style. Use only after the user explicitly requests a commit or push, including /commit or /commit-push. Never infer repeat authorisation from an earlier commit or push; never run raw git commit.
Patterns for working with git branches, remotes, diffs against the default branch, and rebases. Use when resolving rebase conflicts, continuing interactive rebases, amending commits, or any git operation that would open an interactive editor.
Investigate a topic against primary sources and return cited findings, comparing credible maintainer and contributor perspectives when judgement is involved. Use when the user wants a topic researched, docs, API, or spec facts gathered, an external library or GitHub behaviour verified, competing views compared, or reading legwork delegated to a background agent.
Ask minimal clarifying questions only when ambiguity materially changes implementation. Use for routine underspecification; do not use for user-requested light or full grilling, plan stress-testing, or broad design interviews.
Stress-test a plan or proposed change through focused one-question-at-a-time grilling, with light and full intensity. Use when the user says grill, grill me, grill me lightly, ask me a couple of questions, stress-test this plan, or wants question-led scrutiny before planning.
| name | pkexec-root |
| description | Use pkexec first for commands that need root directly or indirectly. |
Use this skill when a command needs root directly or uses sudo internally.
Prefer pkexec first.
For yay, use:
yay -S <pkg> --sudo pkexec --sudoflags ""
yay -U "/path/to/package.pkg.tar.zst" --sudo pkexec --sudoflags ""
For direct pacman commands, use:
pkexec pacman -S <pkg>
pkexec pacman -U "/path/to/package.pkg.tar.zst"
pkexec pacman -R <pkg>
For commands that invoke sudo internally, prefer pkexec first when practical.
If pkexec fails, use the first working alternative below and note which path was used:
yay, fall back to:yay -S <pkg> --sudo sudo --sudoflags ""
yay -U "/path/to/package.pkg.tar.zst" --sudo sudo --sudoflags ""
yay itself is the problem and the package is local, install with pkexec pacman -U ....sudo directly.Commands covered by this skill include:
sudoyay that delegate privileged parts to sudoomarchy commands that perform privileged operations under the hoodExamples of omarchy-* command families that may need this treatment include:
omarchy-install-*omarchy-update-*omarchy-pkg-*omarchy-reinstall*omarchy-refresh-*omarchy-setup-*omarchy-* commands that touch packages, services, boot config, or /etcThis list is not exhaustive.