Menu
Use when user asks to release, publish, or bump version of a Haskell package to Hackage
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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 | hackage-release |
| description | Use when user asks to release, publish, or bump version of a Haskell package to Hackage |
Bump version, build, validate, tag, push, and publish a Haskell package to Hackage.
package.yaml (if using hpack) or .cabal filehpackcabal buildcabal check (must report zero warnings)cabal sdistgit tag vX.Y.Z.Wgit push && git push --tagspass show hackage.haskell.org.gpg
user: line has usernamecabal upload --publish <sdist-tarball> --username=<user> --password='<pass>'cabal haddock --haddock-for-hackage then cabal upload --documentation --publish <docs-tarball> --username=<user> --password='<pass>'Haskell uses the Package Versioning Policy with format A.B.C.D:
| Component | When to Bump |
|---|---|
| A.B (major) | Breaking API changes |
| C (minor) | Backwards-compatible new features |
| D (patch) | Bug fixes, non-API changes |
If the project uses a Nix flake, wrap cabal commands with nix develop:
nix develop --command cabal build
nix develop --command cabal check
nix develop --command hpack package.yaml
Prefer nix develop (flake) over nix-shell (legacy) to avoid ABI mismatches.
Hackage warns about:
text >= 1.2 && < 2.2)< 2 not < 2.0.0; use < 0.4 not < 0.4.0.0Run cabal check to verify zero warnings before releasing.
cabal build succeedscabal check reports no errors or warnings