tree-sitter-language-pack-managing-parsers
Skill480 starsChanged 3 months agoMITView on GitHub
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`.
Files
<!--
AI-RULEZ :: GENERATED FILE — DO NOT EDIT
Content-Hash: blake3:a2e80363e28ad0e5f3112ab4c73c46e76fa6f9a6d875d1c56af89fc86546f9f5
Source-Hash: blake3:e63d5809d1494bcfc9e4a67ba9975f7ed86cda4b3d2bdf85b0c483f0c5ddfcb0
Schema-Version: v1
-->Managing parsers
Parser libraries download on demand the first time a language is used and are cached on disk. Manage that cache explicitly for offline work, CI prefetch, reproducible builds, or to reclaim space.
Note: parser cache management (
download,clean,init) is done via thets-packCLI directly. The OpenCode tools expose only parse/process/info.
Prefetch (offline / CI)
ts-pack download python rust typescript # specific languages
ts-pack download --all # every available language
ts-pack download --groups all # by group
ts-pack download python --fresh # clean cache first, then downloadThe manifest currently defines exactly one group, all. Group names are
manifest data, not a fixed list — enumerate them with manifest_groups()
rather than hardcoding. Run download in your CI setup step so later
parse/process calls hit the cache instead of the network.
Inspect
ts-pack list # all available languages
ts-pack list --downloaded # only languages currently cached
ts-pack list --manifest # everything in the remote manifest
ts-pack list --filter script # filter by name substring
ts-pack info python # known? downloaded? cache path?
ts-pack cache-dir # print the effective cache directoryClean
ts-pack clean # prompts for confirmation
ts-pack clean --force # skip the prompt (use in scripts/CI)clean removes all cached parser libraries; they re-download on next use.
Config file (init)
ts-pack init writes a language-pack.toml to the current directory
pinning a cache location and/or a language set. This writes a file to
the working directory.
ts-pack init --languages python,rust --cache-dir .ts-pack-cacheResulting language-pack.toml:
cache_dir = ".ts-pack-cache"
languages = ["python", "rust"]With no flags, init writes a commented template. When --languages is given,
init also triggers the download for those languages. (init takes only
--languages and --cache-dir — for group-based prefetch use
ts-pack download --groups <names>.) Commit language-pack.toml to pin the
parser set across a team or CI.
Typical CI flow
ts-pack init --languages python,rust,typescript --cache-dir .ts-pack-cache
# ... later steps run parse/process offline against the warm cache ...
ts-pack list --downloaded # assert the expected parsers are presentWhen to reach for the other skills
Once parsers are cached, use tree-sitter-language-pack-parsing-source to get syntax trees and
tree-sitter-language-pack-extracting-code-structure to pull metadata. info/list here also serve
the language-support checks described in tree-sitter-language-pack-detecting-languages.
In this repository15 other files it gives its agents.
- apiSkill
- cliSkill
- mcpSkill
- apiSkill
- cliSkill
- mcpSkill
- apiSkill
- cliSkill
- mcpSkill
- tree-sitter-language-pack-chunking-for-llmsSkill
- tree-sitter-language-pack-detecting-languagesSkill
- tree-sitter-language-pack-extracting-code-structureSkill
- tree-sitter-language-pack-parsing-sourceSkill
- tree-sitter-language-packSkill
- tree-sitter-language-pack-using-the-mcp-serverSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

