Files

Ivan Malison 3bef4d1460 feat: reorganize skills with canonical agents/ locations and symlinks

- Symlink dotfiles/claude/CLAUDE.md -> ../agents/AGENTS.md
- Move global skills to dotfiles/agents/skills/ as canonical location
  (hackage-release, org-agenda-api-production, release)
- Add new taffybar-ecosystem-release skill documenting the taffybar
  package dependency graph and release propagation workflow
- ~/.claude/skills/ entries are now symlinks to canonical locations
- email-cleanup and weekly-scheduling moved to ~/org/agents/skills/
- Removed stale debug-video-processing symlink

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-04-18 19:05:35 -07:00

2.2 KiB

Raw Blame History

name, description

name	description
hackage-release	Use when user asks to release, publish, or bump version of a Haskell package to Hackage

Hackage Release

Bump version, build, validate, tag, push, and publish a Haskell package to Hackage.

Workflow

Bump version in package.yaml (if using hpack) or .cabal file
Update ChangeLog.md with release notes
Regenerate cabal (if using hpack): hpack
Build: cabal build
Check: cabal check (must report zero warnings)
Create sdist: cabal sdist
Commit & tag: commit all changed files, git tag vX.Y.Z.W
Push: git push && git push --tags
Get Hackage credentials: pass show hackage.haskell.org.gpg
- Format: first line is password, user: line has username
Publish package: cabal upload --publish <sdist-tarball> --username=<user> --password='<pass>'
Build & publish docs: cabal haddock --haddock-for-hackage then cabal upload --documentation --publish <docs-tarball> --username=<user> --password='<pass>'

Version Bumping (PVP)

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

Nix-Based Projects

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.

PVP Dependency Bounds

Hackage warns about:

Missing upper bounds: Every dependency should have an upper bound (e.g., text >= 1.2 && < 2.2)
Trailing zeros in upper bounds: Use < 2 not < 2.0.0; use < 0.4 not < 0.4.0.0

Run cabal check to verify zero warnings before releasing.

Checklist

Version bumped in package.yaml / .cabal
ChangeLog.md updated
Cabal file regenerated (if hpack)
cabal build succeeds
cabal check reports no errors or warnings
Changes committed and tagged
Pushed to remote with tags
Package published to Hackage
Docs published to Hackage

2.2 KiB Raw Blame History