القائمة
Use when releasing, version-bumping, or propagating changes across taffybar GitHub org packages (taffybar, gtk-sni-tray, gtk-strut, status-notifier-item, dbus-menu, dbus-hslogger)
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Safely reclaim disk space through reviewed, automated cleanup actions on this machine, especially for Nix, Rust build artifacts, containers, caches, and service state. Use when an assessment has identified cleanup candidates, the user asks to free space or automate remediation, or low-space recovery requires measured deletion of rebuildable data.
Measure and explain disk usage without deleting data, producing reusable compressed ncdu snapshots and an evidence-backed cleanup handoff. Use when disk is low, a filesystem is unexpectedly large, builds fail from space pressure, the user asks what is consuming space, or deeper iterative disk analysis is needed before cleanup.
Safely delegate between Codex and Claude through read-only CLI wrappers. Use when the user explicitly asks Codex or Claude to delegate to the other, or when a workflow explicitly calls for an independent cross-model second opinion.
Use when user wants to find promotional or unwanted recurring emails to unsubscribe from, or when doing periodic inbox hygiene to identify senders worth unsubscribing from
Use when the user wants to reset or rotate a website or service password end-to-end, including finding the right `pass` entry, generating a new password with `xkcdpassgen`, retrieving reset emails through `gws gmail` or a local mail CLI, completing the reset in the browser via the Chrome extension, and updating the password store safely without losing entry metadata.
Use when investigating production org-agenda-api state, testing endpoints, or debugging production issues
| name | taffybar-ecosystem-release |
| description | Use when releasing, version-bumping, or propagating changes across taffybar GitHub org packages (taffybar, gtk-sni-tray, gtk-strut, status-notifier-item, dbus-menu, dbus-hslogger) |
Release and propagate changes across the taffybar Haskell package ecosystem.
See also: taffybar-nixos-flake-chain for how these packages are consumed by the NixOS configuration and what flake.lock updates may be needed after a release.
taffybar
├── gtk-sni-tray
│ ├── dbus-menu
│ ├── gtk-strut
│ └── status-notifier-item
├── dbus-menu
├── gtk-strut
├── status-notifier-item
└── dbus-hslogger
Leaf packages (no ecosystem deps): gtk-strut, status-notifier-item, dbus-hslogger, dbus-menu
Mid-level: gtk-sni-tray (depends on dbus-menu, gtk-strut, status-notifier-item)
Top-level: taffybar (depends on all above)
| Package | GitHub | Local Checkout |
|---|---|---|
| taffybar | taffybar/taffybar | ~/.config/taffybar/taffybar/ |
| gtk-sni-tray | taffybar/gtk-sni-tray | ~/Projects/gtk-sni-tray/ |
| gtk-strut | taffybar/gtk-strut | ~/Projects/gtk-strut/ |
| status-notifier-item | taffybar/status-notifier-item | ~/Projects/status-notifier-item/ |
| dbus-menu | taffybar/dbus-menu | ~/Projects/dbus-menu/ |
| dbus-hslogger | IvanMalison/dbus-hslogger | ~/Projects/dbus-hslogger/ |
Always release leaf packages before their dependents. Changes propagate upward through the graph.
Use the hackage-release skill for the full Hackage publish workflow. In the local checkout:
.cabal file (PVP: A.B.C.D)cabal build && cabal checkcabal sdistvX.Y.Z.W, push with tagsManual doc upload required for GTK-dependent packages: Hackage cannot build documentation for packages that depend on GTK/GI libraries (the build servers lack the system dependencies). This affects taffybar, gtk-sni-tray, gtk-strut, and dbus-menu. For these packages you must build haddocks locally and upload them yourself — see the hackage-release skill for the cabal haddock --haddock-for-hackage and cabal upload --documentation commands. Only status-notifier-item and dbus-hslogger (pure DBus/Haskell deps) can have their docs built by Hackage automatically.
For each package higher in the graph that depends on what you just released, update the dependency bound in its .cabal file. For example, if you bumped gtk-strut to 0.1.5.0:
gtk-sni-tray.cabal: update gtk-strut >= 0.1.5 && < 0.2taffybar.cabal: update gtk-strut >= 0.1.5 && < 0.2Then release those packages too if needed (repeat from step 1).
Each package's flake.nix references its ecosystem dependencies as inputs (typically flake = false pointing at GitHub). After pushing changes, update the flake.lock in any repo that directly references the changed package:
cd ~/Projects/gtk-sni-tray # if it depends on what changed
nix flake update gtk-strut
cd ~/.config/taffybar/taffybar # taffybar references all ecosystem pkgs
nix flake update gtk-strut
gtk-strut, status-notifier-item, dbus-hslogger, dbus-menu (leaves — parallel OK)gtk-sni-tray (update bounds for any leaf changes first)taffybar (update bounds for all changes)