How to use

Every form exists as an SDK option first and the CLI is a thin client of it.

One snippet from stdin

cat snippet.ts | jint run str -                # extensionless: hint the grammar
cat snippet.go | jint run str - --language go

Directories

jint run src/

Single file

Explicit paths.

jint run src/a.ts

Path list

git diff --name-only HEAD~1 | jint run paths -
jint run paths - < list.txt

Useful for a pre-commit hook.

One element

jint run src/a.ts@L58                # element whose span contains line 58: one classifier call
jint run src/a.ts@L40-80             # every element fully enclosed in the range
jint run src/a.ts@L40-80 --rule is_function_srp

Pre-commit and CI

jint is a CLI, so you can embed it in the part of the pipeline you find most suitable: CI or a pre-commit hook. A pre-commit hook is advised as it returns an action for the agent to take: the rule’s handle gives a severity and a message that says what to do. An error fails the hook and sets the exit code, so the agent has to act on it before the work goes through.

Skills

The CLI carries jint’s agent skills: jint-follow runs jint and resolves its findings, jint-author writes and calibrates rules, and jint-propose turns what you expect into rules. Write them into your agent’s skills directory, one folder per skill:

jint skills export .claude/skills