AGENT SKILL

tree-sitter-language-pack-detecting-languages

Use when the user wants to know which programming language a file or snippet is. Covers implicit detection in `ts-pack parse`/`process`, confirming support with `ts-pack list`/`info`, and the SDK detection functions for path, extension, and raw content.

License 许可
MIT
最近更新
2026-11-07
Stars
★ 485
Forks
71

01 前言 Front Matter

name
tree-sitter-language-pack-detecting-languages
description
Use when the user wants to know which programming language a file or snippet is. Covers implicit detection in `ts-pack parse`/`process`, confirming support with `ts-pack list`/`info`, and the SDK detection functions for path, extension, and raw content.

02 资源文件 1

03 SKILL.md 正文

<!-- AI-RULEZ :: GENERATED FILE — DO NOT EDIT Content-Hash: blake3:1652855d0d25051247e7728976192ad988833c4913509f8924c67d16628472c6 Source-Hash: blake3:b8687cf31ac8c66a5ecc15c4f11520ff201d8db14467b7528d5120124e9753a4 Schema-Version: v1 -->

Detecting languages

tree-sitter-language-pack maps a file to one of 371 supported languages. Detection works from a file path, a bare extension, or — via the SDK — the file content itself.

On the CLI: detection is implicit

There is no standalone ts-pack detect command. parse and process auto-detect the language from the file extension and act on it:

ts-pack parse src/app.ts      # detects "typescript", parses
ts-pack process app.py        # detects "python", extracts

When detection fails (no extension, ambiguous, or stdin), pass --language:

cat snippet | ts-pack parse - --language go

To check whether a language name is supported and cached without parsing anything, use list and info:

ts-pack list --filter type      # languages whose name contains "type"
ts-pack list --manifest         # every language in the remote manifest
ts-pack info typescript         # is it known? is it downloaded? cache path?

In the SDK: explicit detection

The core exposes three detection functions, including content-based detection that the CLI does not surface:

Function Detects from
detect_language_from_path(path) Full path (uses the extension).
detect_language_from_extension(ext) A bare extension like "rs".
detect_language_from_content(content) Raw source text — no path needed.

Each returns the language name or null/None when no grammar matches.

Python

from tree_sitter_language_pack import (
    detect_language_from_path,
    detect_language_from_extension,
    detect_language_from_content,
)

detect_language_from_path("src/app.py")      # "python"
detect_language_from_extension("rs")          # "rust"
detect_language_from_content(open("x").read())  # from the shebang line, if present

Node.js / TypeScript

import { detectLanguageFromPath, detectLanguageFromContent } from "@xberg-io/tree-sitter-language-pack";

const lang = detectLanguageFromPath("src/app.ts") ?? detectLanguageFromContent(source);

Choosing CLI vs SDK

  • Path or extension is enough, one-shot → just run ts-pack parse/process and let it auto-detect.
  • Only raw content (a pasted snippet, a stream, a file with no extension) → use the SDK's detect_language_from_content, then pass the result as --language to the CLI if needed.

When to reach for the other skills

Once the language is known, hand off to tree-sitter-language-pack-parsing-source (syntax tree) or tree-sitter-language-pack-extracting-code-structure (metadata). To see or prefetch the parser for a detected language, see tree-sitter-language-pack-managing-parsers.

04 同仓库更多 Skills

xberg-io
xberg-io/tree-sitter-language-pack

tree-sitter-language-pack

Parse and extract code intelligence from 371 programming languages using tree-sitter grammars. Use when writing code that parses source, extracts structure/imports/exports/symbols/docstrings/comments, detects a language, runs syntax diagnostics, or produces syntax-aware chunks for LLMs — in Rust, Python, Node.js/TypeScript, or the ts-pack CLI. Covers installation, the CLI surface, the SDK surface, and parser-cache management.

开发工程师
★ 485
xberg-io
xberg-io/tree-sitter-language-pack

tree-sitter-language-pack-using-the-mcp-server

Use when parsing source, extracting code structure, or detecting a language through the tree-sitter-language-pack MCP server's tools, rather than shelling out to the ts-pack CLI. Covers the tool surface, the auto-installing launcher, and when MCP beats the CLI or SDK.

后端与接口Skill与智能体开发
★ 485
xberg-io
xberg-io/tree-sitter-language-pack

tree-sitter-language-pack-parsing-source

Use when the user wants a tree-sitter syntax tree for a source file — an s-expression dump or JSON tree. Covers `ts-pack parse`, language auto-detection vs `--language`, stdin input, and reading `has_errors`.

★ 485
xberg-io
xberg-io/tree-sitter-language-pack

tree-sitter-language-pack-managing-parsers

Use when the user needs to manage the tree-sitter parser cache — prefetch parsers for offline or CI runs, list what is downloaded, inspect a language, find the cache directory, or clean it. Covers `ts-pack download`, `list`, `info`, `cache-dir`, `clean`, and `init`.

★ 485
xberg-io
xberg-io/tree-sitter-language-pack

tree-sitter-language-pack-extracting-code-structure

Use when the user wants structured code metadata from a source file — functions, classes, imports, exports, symbols, docstrings, comments, or syntax diagnostics. Covers `ts-pack process` feature flags, the JSON result shape, and the default feature set.

开发工程师
★ 485
xberg-io
xberg-io/tree-sitter-language-pack

tree-sitter-language-pack-chunking-for-llms

Use when the user wants to split source code into chunks for an LLM context window without breaking syntax mid-construct. Covers `ts-pack process --chunk-size`, why syntax-aware splits beat fixed-byte splits, picking a size, and the chunk JSON shape.

★ 485