Personal helper packages for CI, testing and tooling, published under the @lhechenberger npm scope. A Bun workspaces monorepo; every package is documented in its own README, which is what the npm page shows.
| Package | Description |
|---|---|
@lhechenberger/check-links |
Broken-link crawler for deployments that separates flaky failures |
skills/ and agents/ hold generic skills and agents that are installed with bunx skills add LukasHechenberger/workbench -s <name>; see skills/README.md.
bun install
bun run check # tsc (TypeScript 7), oxlint and oxfmt
bun run testCreate packages/<name> with package.json (@lhechenberger/<name>, "publishConfig": {"access": "public"}), a README that explains installation, configuration and setup completely (the npm page is the documentation), and a src/. Add it to the table above.
Changesets: bun run changeset per change, merge to main; the CI workflow opens a version PR and publishes to npm when it is merged. Publishing uses npm trusted publishing (no npm token): each package needs a trusted publisher for LukasHechenberger/workbench, workflow ci.yml, with "Allow npm publish" (configure it on npmjs.com after the first publish). Needs the repository secret CHANGESETS_GITHUB_TOKEN (a personal access token with contents and pull-requests write access, so the version PR triggers CI).
This repository is open source (MIT). Packages must be generic: no names, paths, URLs, IDs or configuration of real projects, customers or companies, and no secrets. Project-specific settings (skip lists, rules) live in the consuming project, never here; examples use example.com. See AGENTS.md; the public-repo-guard agent checks this.