feat(lint): migrate to prek/pixi and enforce conventional commits with commitizen

[olantwin]

Migrates shipdist onto the org's prek/pixi linting standard and enforces Conventional Commits with commitizen (replacing crate-ci/committed).

• New pixi.toml with a lint environment providing prek, commitizen, shellcheck, and alidistlint/yamllint (PyPI, pinned to the previous hook rev v1.7.5).
• .pre-commit-config.yaml rewritten in prek style: pre-commit-hooks builtins run natively; alidistlint (with its upstream files: \.sh$ filter) and the commitizen commit-msg hook run via the pixi env.
• New .github/workflows/lint.yml calling the shared prek.yml and commit-check.yml reusable workflows.
• Removes committed.toml and the pre-commit.ci ci: block; linting now runs through the prek workflow.

Verified locally: pixi run lint (prek on all files) exits clean, and cz check accepts a Conventional message. All recent commit history already uses standard types.

Depends on ShipSoft/.github#13 (adds commit-check.yml).

[coderabbitai]

Warning

Review limit reached

@olantwin, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 54 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: c145c3d5-e1e5-486c-8775-7f98065fdabd

📥 Commits

Reviewing files that changed from the base of the PR and between 94c954a and 05ff85b.

⛔ Files ignored due to path filters (1)

• pixi.lock is excluded by !**/*.lock

📒 Files selected for processing (4)

• .github/workflows/lint.yml
• .pre-commit-config.yaml
• committed.toml
• pixi.toml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/prek-commitizen

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}