メニュー
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)
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/colonelpanic8/dotfiles --skill taffybar-ecosystem-releaseコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Answer questions about the Paseo product and app, including setup, configuration, connectivity, providers, workspaces, updates, logs, and troubleshooting. Use when a user inside Paseo asks how Paseo works, how to configure it, or why something is broken; use the paseo skill instead to operate agents and workspaces through MCP or the CLI.
Build and manage trusted local Paseo plugins. Use when the user asks to create, edit, install, reload, enable, disable, remove, or troubleshoot a Paseo plugin; add a native surface or sidebar item; use Paseo from plugin code; add plugin RPCs; or contribute composer attachments.
Shape output for a reader with ADHD: lead with the next action, number multi-step work, restate state across turns, suppress tangents, give specific time estimates, make wins visible. Invoke with /i-have-adhd; stays on until "stop adhd mode".
| 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)