Count Lines of Code

Overview

When you supply source files, we count physical, blank, comment, code, and mixed lines per file using a lexical pass that respects string literals. Language is detected from the path extension unless you set it explicitly. We do not parse semantics, execute code, or walk a filesystem — do not use this for complexity metrics or AST analysis.

Naive line counters misclassify comments inside strings. We use the same lexical rules every time so your ratios stay trustworthy.

When to use it

Scope

Non-goals

• Does not parse or execute code
• Does not compute complexity metrics
• Does not walk a filesystem
• Does not infer language from file content prose

Properties

Capabilities

Cost & billing

Flat rate per invocation

File handling

File limits

Constraints this skill applies to your input and generated files. The “Limited by” column shows the static source of each cap; none of these can be raised by upgrading your plan.

How we handle your data

Input schema

Output schema

API contract

curl -sS -X POST "$BASE/v1/execute" -H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' -d '{"skillKey":"code.count_loc","input":{"files":[{"path":"a.py","content":"# c\nx=1\n"}]}}'

import { Squillify } from "@squillify/sdk";

const sq = new Squillify({ apiKey: process.env.SQUILLIFY_API_KEY });

const { output } = await sq.execute("code.count_loc", {"files":[{"content":"// c\nclass A {}\n","path":"Main.java"}]});

Errors

Other limits

Limitations

• Does not parse or execute code
• Does not compute complexity metrics
• Does not walk a filesystem
• Does not infer language from file content prose
• Cyclomatic complexity
• Semantic or AST-based analysis

How to call

POST /v1/execute (requires authentication)

{
  "skillKey": "code.count_loc",
  "input": {
    "files": [
      {
        "content": "// c\nclass A {}\n",
        "path": "Main.java"
      }
    ]
  }
}

Examples

{
  "files": [
    {
      "content": "// c\nclass A {}\n",
      "path": "Main.java"
    }
  ]
}

{
  "totals": {
    "physical": 2,
    "blank": 0,
    "comment": 1,
    "code": 1,
    "mixed": 0
  },
  "warnings": [],
  "byLanguage": {
    "java": {
      "physical": 2,
      "blank": 0,
      "comment": 1,
      "code": 1,
      "mixed": 0
    }
  },
  "files": [
    {
      "physical": 2,
      "blank": 0,
      "comment": 1,
      "code": 1,
      "mixed": 0,
      "path": "Main.java",
      "language": "java",
      "confidence": "extension",
      "supported": true,
      "bytes": 16
    }
  ]
}

{
  "files": [
    {
      "content": "hello\n",
      "path": "notes.xyz"
    }
  ]
}

{
  "totals": {
    "physical": 0,
    "blank": 0,
    "comment": 0,
    "code": 0,
    "mixed": 0
  },
  "byLanguage": {},
  "files": [
    {
      "path": "notes.xyz",
      "supported": false,
      "language": "unknown",
      "bytes": 6
    }
  ],
  "warnings": [
    {
      "code": "LOC_LANGUAGE_UNSUPPORTED",
      "message": "Unsupported/unknown language for notes.xyz",
      "severity": "warning"
    }
  ]
}

Recommended use cases

• Report code versus comment ratios in CI
• Measure supplied source size by language
• Aggregate LOC across a bounded file batch

Avoid for

• Cyclomatic complexity
• Semantic or AST-based analysis

Related skills

Composable with

Safety & privacy

• Runs without calling any external service.
• Your payloads are never stored permanently.
• Telemetry captures metadata only — never your payload contents.
• We never train models on your payloads.
• No human reviews your payloads.

Tags