Get semantic lint reports in under 2 minutes.

1. Initialize Configuration

Run this in your project root:

lintent init --preset python

lintent init --preset typescript

This creates lintent.yaml with semantic rules for common lint violations.

2. Run lintent

lintent run --pretty

3. Understand the Output

{
  "violations": [
    {
      "file": "src/main.py",
      "line": 3,
      "column": 8,
      "tool": "ruff",
      "code": "F401",
      "message": "`os` imported but unused",
      "semantic": {
        "illegal": "Importing modules that are not used",
        "legal": "Only import what you use, or mark with # noqa: F401 if for side-effects",
        "why": "Clean dependency graph, faster startup, clearer code"
      }
    }
  ],
  "linters": {
    "detected": ["ruff", "pyright"],
    "results": [
      { "name": "ruff", "status": "success", "violations_count": 5 },
      { "name": "pyright", "status": "not_found", "error": "..." }
    ]
  },
  "summary": {
    "total": 5,
    "with_semantic": 5,
    "without_semantic": 0,
    "files_affected": 2
  }
}

What Each Field Means

4. Fix With Understanding

When fixing violations:

1. Read semantic.legal - It tells you the correct pattern
2. Read semantic.why - Understand the reasoning
3. Fix with intent, not just to silence the error

What's Next?

• Configuration → - Customize your semantic rules
• Concepts: Semantic Rules → - Deep dive on illegal/legal/why
• CLI Reference → - All commands and options