Repository navigation
Conversation
The skill named `omarchy pkg add` twice in passing but never said that `pacman`, `yay`, and `paru` are off the supported path, never mentioned `omarchy pkg drop`, and carried no warning against `pacman -Syu`. Its triggers also omitted packages and updates entirely, so the skill often did not load for "install X" or "update my system" in the first place. Add a Package Management section covering the wrappers, the update guard and its deliberate bypass, and the read-only pacman queries that need no wrapper. Extend the triggers, the decision framework, and the examples to match. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
+1 on this. Agents rarely load the skill for system tasks beyond desktop config, even though the skill body covers them. It would help to widen the description to cover general system administration on Omarchy (installing and removing software, default apps, updates, troubleshooting), in whatever form you think fits best. |
|
Reviewed at a5dda7d, nothing found. This touches one Markdown file, so nothing was run: I checked each thing it names against current
Codex Medium reviewed the same diff as a second opinion. It found nothing wrong and agreed on each point above. It had access to this review's reasoning, so its agreement is not guaranteed to be independent. Related, and not duplicates: #6718 restructures the skill and adds its own packages section, and #11804 changes the Privilege Escalation section to have agents retry with Nothing is waiting on you. This now waits on the maintainer. |
The only conflict was the skill's trigger list, which quattro widened (window behavior, widgets, fonts, screen recording, appearance changes) while this branch added the package-management triggers. Keep quattro's list and append the package sentence to it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
This stopped merging cleanly once
Nothing was run, since this is one Markdown file. Codex Medium reviewed the merged result as a second opinion and found nothing wrong. It had access to this review's reasoning, so its agreement is not guaranteed to be independent. Overlaps for whoever lands second: #9227 rewrites the same decision-framework line to require an explicit request before any AUR install, and #6718, #11804 and #14499 also touch package or privilege guidance in this skill. This now waits on CI finishing and then on the maintainer. Nothing is needed from you. |
|
| When Omarchy ships an installer for the software, prefer it over a bare | ||
| `omarchy pkg add` — it also wires up configuration, services, and launcher | ||
| entries. Check `omarchy install --help` before falling back to `omarchy pkg`. |
There was a problem hiding this comment.
The new guidance prefers dedicated installers, but only points to omarchy pkg drop for removal. For software with a dedicated remover, this can leave broken settings behind. For example, dropping voxtype-bin leaves its user service enabled and can leave voxtype selected as the dictation backend.
Prefer dedicated removers too: check omarchy remove --help before falling back to package removal.
| When Omarchy ships an installer for the software, prefer it over a bare | |
| `omarchy pkg add` — it also wires up configuration, services, and launcher | |
| entries. Check `omarchy install --help` before falling back to `omarchy pkg`. | |
| When Omarchy ships an installer for the software, prefer it over a bare | |
| `omarchy pkg add` — it also wires up configuration, services, and launcher | |
| entries. Check `omarchy install --help` before falling back to `omarchy pkg`. | |
| Likewise, prefer a dedicated remover when one exists so services, settings, | |
| and launcher entries are cleaned up. Check `omarchy remove --help` before | |
| falling back to `omarchy pkg drop`. |
Knowledge Base Used: Package management and curated installs
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
Why
The manual is explicit that Omarchy owns package management: Other Packages documents
omarchy pkg add/omarchy pkg drop, and Updates warns against runningpacman -Syuoryay -Syudirectly because it risks missing the config updates that support newer library versions.00-omarchy-update-guard.hookalready enforces the update half at the libalpm level.The installed agent skill did not carry any of that. It named
omarchy pkg addtwice in passing — one table row and one line in the decision framework — never mentionedomarchy pkg drop, and never said thatpacman,yay, andparuare off the supported path. An agent reading it has no reason not to reach forsudo pacman -S.Its triggers also omitted packages and updates entirely, so the skill often never loaded for "install X" or "update my system" in the first place — the same gap #8257 fixed for
~/.config/systemd/user/.This surfaced on a real 4.0.3 install: the agent kept offering bare
pacmancommands, and the user had to point at the manual to correct it.What
pkg add/pkg aur add/pkg drop/ the fuzzy-finder pickers /present/missing/omarchy update), a pointer to preferomarchy install ...where an installer exists, and thepacman -Syuprohibition with whatomarchy updateactually does that a bare upgrade skips.pacman -Q,-Qi,-Ql,-Qo,-Si,-Ss,-Sl,yay -Ss/-Si) are called out as safe to run directly, so the rule doesn't over-fire on inspection — the skill's ownomarchy pkg present/missingare thin wrappers aroundpacman -Q.Docs only; no behavior change.
Related
#6718 restructures the skill and adds a "Packages and Optional Software" section to a new
system.md. It lists the same wrappers but does not prohibit the raw tools, mention the update guard, or extend the triggers. This change is scoped to the currentSKILL.mdso it applies cleanly either way; happy to fold it intosystem.mdinstead if #6718 lands first.Testing
./test/clipasses../test/allreports 6 failing files undertest/shell.d/(bar-icon-geometry,config,locate,runtime-smoke,snapper,unowned-system-paths), but all 6 fail identically on the unmodified base commit in this environment — pre-existing and untouched by a markdown-only change.🤖 Generated with Claude Code