casomoltd

@casomoltd/tooling

Shared linting, formatting, commit config, and CLI tools for Casomo Ltd's repos.

What's included

Exports

Export	Description
@casomoltd/tooling/eslint	createBaseConfig() — ESLint flat config with Next.js, TypeScript, and SonarJS
@casomoltd/tooling/eslint-lib	ESLint config variant for library packages
@casomoltd/tooling/prettier	Prettier config object
@casomoltd/tooling/commitlint	commitlint config with no-ai-attribution plugin
@casomoltd/tooling/knip	Knip config for unused exports/dependencies
@casomoltd/tooling/jscpd	Copy-paste detection config
@casomoltd/tooling/readability	scoreText() — readability scoring for page content

Bin commands

Command	Description
check-version	Pre-push guard — rejects push if package.json version hasn't changed vs origin/main
pre-push	Husky pre-push hook — runs check, build, then version/tag guards
pre-commit	Husky pre-commit hook — runs npm run check
commit-msg	Husky commit-msg hook — runs commitlint
readability	Measure reading difficulty of page content
screenshot	Capture a dev server page via Puppeteer

Install

Consumed as a git dependency — it's shared config + CLI scripts, not a registry package. Add it to a consumer's devDependencies:

"@casomoltd/tooling": "github:casomoltd/tooling#semver:^0.10.0"

The repo is public, so installs need no token. The files allowlist plus the verify-pack leak-gate keep the installed surface to configs/CLI only.

Husky hooks

The package provides shared hook commands so all repos enforce the same standards. Wire them up in .husky/:

.husky/pre-commit

pre-commit

.husky/commit-msg

commit-msg $1

.husky/pre-push

pre-push

Each repo defines its own check script in package.json — the hooks call npm run check which runs whatever checks that repo needs (lint, typecheck, spell, etc.).

Note: The tooling repo itself calls scripts by path in its hooks (e.g. ./bin/check-version.sh) because it can't resolve its own bin commands via node_modules/.bin.

Screenshot tool

Capture the running dev server for visual inspection:

npm run ss              # 1280×800 desktop capture
npm run ss contact      # desktop capture of /contact
npm run ss -- --width 390 --height 844   # mobile capture
npm run ss contact --width 390           # mobile /contact

Options:

Flag	Default	Description
--width <n>	1280	Viewport width in pixels
--height <n>	800	Viewport height in pixels

Add these scripts to your package.json:

{
  "screenshot": "screenshot",
  "ss": "npm run screenshot --"
}

Screenshots are saved to .claude/screenshots/. Set SCREENSHOT_URL to override the default http://localhost:3000.

Quality gates

There is no CI — all quality gates run locally via git hooks. Code should be deployment-ready by the time it's pushed to the remote.

• pre-commit: Runs commitlint only (fast).
• pre-push: Runs the full suite — npm run check, npm run build, then version and tag guards. This ensures lint, typecheck, spelling, and version bumps are all verified before code reaches the remote.

Usage

.prettierrc.js

module.exports = require('@casomoltd/tooling/prettier');

commitlint.config.cjs

module.exports = require('@casomoltd/tooling/commitlint');

eslint.config.mjs

import { createBaseConfig } from '@casomoltd/tooling/eslint';

The ESLint config uses a factory function that receives resolved imports from the consumer to avoid module resolution issues across package boundaries.

Local development

Changes to tooling require a push to main to publish (the workflow runs automatically). Consuming repos then pick up changes with npm update @casomoltd/tooling.

For fast iteration while editing tooling config locally, use npm link to temporarily symlink your local checkout:

# in the consuming repo
npm link ../tooling

This overrides the published version until the next npm install, which restores the registry version.

Claude Code skills (plugin)

This repo is a Claude Code plugin (.claude-plugin/) shipping the generic, public engineering standards we work to across three agent-facing surfaces — skills, hooks, and agents. Business-specific ones live in private workspace config, not here.

The tooling serves three consumers: Claude (the editing workflow) → these plugin surfaces; CI + git-hooks (automation) → the npm bin scripts; manual human CLI is no longer a design target.