skit-cli 0.2.0__tar.gz → 0.3.0__tar.gz

{skit_cli-0.2.0 → skit_cli-0.3.0}/PKG-INFO

@@ -1,8 +1,8 @@
 Metadata-Version: 2.4
 Name: skit-cli
-Version: 0.2.0
-Summary: Script launcher and parameter manager: all your scripts in one menu, their flags, input() calls, and constants auto-extracted into a run form — no more opening an IDE just to tweak a value.
-Keywords: script,launcher,uv,tui,pep723,script-manager,script-runner,automation,ai-agent,agent-skills
+Version: 0.3.0
+Summary: Launcher and parameter manager for scripts, prompts, programs, and commands: one library, one run form, nothing to memorize.
+Keywords: script,launcher,uv,tui,pep723,script-manager,script-runner,automation,ai-agent,ai-prompt,agent-skills
 Author: Yi-Ting Chiu
 Author-email: Yi-Ting Chiu <mytim710@gmail.com>
 License-Expression: MIT
@@ -20,9 +20,14 @@ Classifier: Topic :: Software Development :: Build Tools
 Classifier: Topic :: Utilities
 Requires-Dist: typer>=0.26,<1
 Requires-Dist: platformdirs>=4.10,<5
+Requires-Dist: packaging>=24,<27
 Requires-Dist: tomli-w>=1.2,<2
 Requires-Dist: textual>=8.2,<9
 Requires-Dist: rich>=15,<16
+Requires-Dist: tree-sitter>=0.25,<0.27
+Requires-Dist: tree-sitter-bash>=0.25,<0.26
+Requires-Dist: tree-sitter-javascript>=0.25,<0.26
+Requires-Dist: tree-sitter-typescript>=0.23,<0.24
 Requires-Python: >=3.12
 Project-URL: Repository, https://github.com/t41372/skit
 Project-URL: Issues, https://github.com/t41372/skit/issues
@@ -41,9 +46,9 @@ Description-Content-Type: text/markdown
 
 **English** | [繁體中文](./README.zh-TW.md) | [简体中文](./README.zh-CN.md)
 
-**skit is a launcher and a home for your Python scripts.**
+**skit is a launcher and a home for your scripts.**
 
-skit stores your Python scripts in one place and makes them painless to launch.
+skit stores your scripts in one place and makes them painless to launch.
 
 **AI writes the scripts. skit gives them a home.**
 
@@ -55,19 +60,21 @@ script, and (with your OK) saving the good ones back, so they outlive the chat.
 
 ## What it does
 
-- **One home for your scripts.** `skit add` collects scattered scripts into a searchable library — keep a copy in the library, or reference the original file.
-- **Parameters without the pain.** Flags, `input()` calls, and the constants you tick become form fields (choices → pickers, booleans → checkboxes, types enforced).
+- **One home for your scripts and prompts.** `skit add` collects scattered scripts and prompts into a searchable library — keep a copy in the library, or reference the original file. Run it bare and it asks what you're adding; hand it a file it can't classify and it asks which kind, instead of erroring out.
+- **Parameters without the pain.** Flags, `input()` calls, and the constants you tick become form fields (choices → pickers, booleans → checkboxes, paths → completion and a file browser, types enforced).
+- **Paths you don't have to type.** Path fields complete as you type — press `→` to accept the suggestion — and `Ctrl+T` → *File or folder…* opens a browsable picker, so you never hand-type a directory again.
 - **It remembers.** Last-used values come back automatically; save favorites as named presets. Parameters marked secret never touch disk. Tokens like `{cwd}` and `{today}` keep presets portable.
-- **No environment mess.** skit declares each script's dependencies in the script itself (PEP 723) and runs it through uv in an isolated, cached environment — no venvs to manage, nothing installed globally.
+- **No environment mess.** Python scripts declare their dependencies inline (PEP 723) and run via uv in isolated environments; JS/TS scripts get a per-script `node_modules`, installed from their declared packages on first run. Nothing global either way. Other languages use the tools already on your machine — skit checks that declared external commands are on your `PATH` before running.
 - **Mouse or keyboard.** Plain `skit` opens the full TUI; every key hint on screen is also a clickable button.
 - **Automation-ready.** Every TUI action is also a CLI command with `--json` output and meaningful exit codes — for shell scripts, CI, and AI agents.
-- **Your agent's script library too.** The official [Agent Skill](https://agentskills.io) teaches Claude Code, Codex, Cursor, Gemini CLI, and friends the whole drill: discover scripts with `skit list`, read a parameter schema with `skit show`, run with `skit run --set … --no-input`. One `skit agent install` away — see [Works with your AI agent](#works-with-your-ai-agent).
+- **Prompts are first-class library entries.** Store a parameterized prompt (managed `{{placeholders}}` become form fields) and fire it at your coding agent — claude, codex, opencode, and friends are preconfigured runners, and any CLI is one `skit runner add` away.
+- **Your agent's library too.** The official [Agent Skill](https://agentskills.io) teaches Claude Code, Codex, Cursor, Gemini CLI, and friends the whole drill: discover entries with `skit list`, read a parameter schema with `skit show`, run with `skit run --set … --no-input`. One `skit agent install` away — see [Works with your AI agent](#works-with-your-ai-agent).
 - **Speaks your language.** English, 繁體中文, and 简体中文, with more to come. See [Languages](#languages).
 
 | Problem | What skit does |
 | --- | --- |
 | Scripts scattered all over the place | One central menu, with search |
-| Scripts with weird external dependencies | An isolated environment per script — dependencies declared in the file (PEP 723), resolved by uv |
+| Scripts that need specific packages or tools | Per-script dependencies for Python (PEP 723 + uv) and JS/TS (npm); for any language, skit checks declared external commands on your `PATH` |
 | CLI flags you forget ten minutes later, `input()` prompts, hard-coded constants meant to be edited by hand | Static analysis extracts them all into an interactive form — no code changes. Last-used values come prefilled; favorites save as presets. |
 | The weird script an AI wrote for you dies with the chat session | Agents check the library first, reuse what's there, and save the keepers — one-off scripts become permanent, parameterized tools |
 
@@ -84,6 +91,34 @@ Nothing to set up per script — no refactoring, no config to maintain. The scri
   <em>Fully mouse operable — every key hint on screen is also a button.</em>
 </p>
 
+## Language support
+
+Python, shell, and JS/TS get static parameter detection **and** value injection. The rest launch out of the box, accept declared parameters, and work with their own CLI parsers.
+
+| Kind | Runs via | Params detected | Injection | Reads its own CLI | Deps / needs |
+| --- | --- | --- | --- | --- | --- |
+| **Python** | `uv run --script` | constants, `input()` | ✅ | argparse · click · typer | PEP 723 (uv) + needs |
+| **Shell** (bash/sh/zsh) | interpreter | constants, `${VAR:-}` env-defaults, `read` | ✅ | getopts | needs |
+| **JS / TS** | deno › bun › node | `const` | ✅ | `util.parseArgs` | npm (per script) + needs |
+| **fish** | fish | `set -q NAME; or set NAME …` env-defaults | — | `argparse` builtin | needs |
+| **PowerShell** | pwsh | — | — | `param()` | needs |
+| **Ruby · Perl · Lua · R** | interpreter | — | — | — | needs |
+| **Programs** (exe) | direct exec | — | — | — | needs |
+| **Commands** | template fill | — | — | — | needs |
+| **Prompts** | your agent CLI (claude · codex · …) | `{{name}}` placeholders | — | — | needs |
+
+You can also declare parameters by hand for any kind — so even plain executables and command templates get the same form / preset / `--set` experience. **needs** are external commands — skit checks they're on your `PATH` before each run (any kind). Python and JS/TS get isolated per-script package dependencies: uv resolves the PEP 723 block, and npm-style deps install into a `node_modules` next to the stored copy (`skit add` suggests them from the script's own imports). Managed JS/TS deps apply to copied entries — a referenced script keeps using its own project's `node_modules` — and installs never run package lifecycle scripts (npm and bun get `--ignore-scripts`; deno skips them by default). One more evener: when deno is the runner skit picks, it passes `--allow-all`, so the same script behaves the same under deno, bun, and node. skit bootstraps uv for Python, but never a JS runtime — you supply node, bun, or deno.
+
+### Prompts
+
+A prompt entry is a reusable, parameterized piece of text for an AI coding agent. Add a `.prompt.md` file (or draft one with `skit add --prompt`); in interactive add review, choose which detected `{{placeholders}}` become form fields. Up to 30 are selected by default; when detection exceeds 30, none are selected by default, so code samples are not mistaken for variables. Managed fields get the full preset / last-values / `--set` experience. There are no escape sequences to learn: anything that isn't a placeholder you manage — unmanaged `{{holes}}` included — travels to the agent byte-for-byte as written, and a per-prompt switch (`--no-interpolate`, or one checkbox in Entry settings) turns insertion off entirely for prompts that were never written with it in mind. Running one renders the text and invokes the selected runner's configured argv command with it. The bundled Claude, Codex, OpenCode, and Antigravity commands open their interactive sessions; Amp is the deliberate exception, using its official `amp -x` one-shot mode to execute the prompt and return. The **runner** is picked on the run form (or pinned per prompt), claude / codex / opencode / amp / antigravity come preconfigured, and `skit runner add mycli -- mycli run {{prompt}}` registers anything else. The rendered prompt travels as a single process argument — no shell in between. One honest caveat: prompts are not a secrets channel — whatever the rendered text contains ends up in the receiving agent's own session logs.
+
+```bash
+skit add review.prompt.md            # managed placeholders become form fields
+skit run review                      # pick the agent, fill the form, go
+skit run review --runner codex --set target=src/app.py --no-input
+```
+
 ## Install
 
 skit is built on [uv](https://docs.astral.sh/uv/) (tested against 0.11.26). Don't have it? skit asks first, then downloads a pinned uv into its own private directory — your `PATH` and global environment stay untouched. A system-wide [install](https://docs.astral.sh/uv/getting-started/installation/) is still preferred.
@@ -131,7 +166,7 @@ That removes skit and its `PATH` shim. Your library and settings live **outside*
 | **Linux** | `~/.local/share/skit` · `~/.local/state/skit` · `~/.config/skit` |
 | **Windows** | `%LOCALAPPDATA%\skit` |
 
-They hold your script library, config, presets, and last-used values — plus, if skit ever bootstrapped its own uv, the private `uv` binary (in `…/skit/bin`, deleted along with the rest).
+They hold your tool library, config, presets, and last-used values — plus, if skit ever bootstrapped its own uv, the private `uv` binary (in `…/skit/bin`, deleted along with the rest).
 
 ```bash
 # macOS
@@ -154,6 +189,7 @@ Two commands are the whole interface:
 
 ```bash
 skit add my_script.py   # add a script
+skit add                # not sure what you're adding? it asks
 skit                    # open the menu, pick it, fill in the form, run
 ```
 
@@ -167,6 +203,7 @@ skit run my_script --dry-run  # print the exact command, don't run it
 skit run my_script --set width=800 --no-input   # set values explicitly, never prompt
 skit show my_script --json    # one script's full parameter schema, machine-readable
 skit params my_script         # show managed parameters and last-used values
+skit deps my_script --dep "requests>=2"   # set a script's package dependencies
 skit list --json              # machine-readable listing
 skit config                   # settings: language, editor, mirror, form style
 skit --help                   # everything else
@@ -199,18 +236,23 @@ skit follows your system language; switch it in the TUI preferences (for automat
 
 ## Mainland China (中国大陆)
 
-Three downloads tend to fail in mainland China: PyPI packages, the Python builds uv fetches from GitHub, and skit's own uv bootstrap. skit can route all three through domestic mirrors.
+Four downloads tend to fail in mainland China: PyPI packages, npm packages, the Python builds uv fetches from GitHub, and skit's own uv bootstrap. skit can route all four through domestic mirrors.
+
+Mirror settings live inside skit only: your global uv config is never touched, and existing mirror settings (`UV_DEFAULT_INDEX`, `uv.toml`, …) are respected. The npm registry rides `NPM_CONFIG_REGISTRY`: an existing value of that variable in your environment still wins, but note npm itself ranks it above `~/.npmrc`.
 
-Mirror settings live inside skit only: your global uv config is never touched, and existing mirror settings (`UV_DEFAULT_INDEX`, `uv.toml`, …) are respected.
+Each ecosystem is its own, independent choice — mirror vendors differ per ecosystem, so no single vendor name spans them:
 
-- **First run**: if PyPI/GitHub look unreachable, skit offers to turn mirrors on — just press Enter.
-- **Any time**: TUI Preferences → mirror, or:
+- **First run**: if PyPI/GitHub look unreachable, skit offers mirror setup — one question per ecosystem, Enter accepts each one's recommended preset.
+- **Any time**: TUI Preferences → mirrors, or:
 
 ```bash
-skit config mirror tsinghua   # or: aliyun / ustc / custom / off
+skit config mirror.pypi tsinghua    # Python packages: tsinghua / aliyun / ustc / a URL / off
+skit config mirror.github nju       # Python builds + the uv binary: nju / an https:// base URL / off
+skit config mirror.npm npmmirror    # JS/TS packages: npmmirror / a URL / off
+skit config mirror off              # master switch: off keeps the URLs; `on` restores them
 ```
 
-Defaults: PyPI via Tsinghua / Aliyun / USTC; Python builds and the uv binary via NJU. Pick `custom` to swap any URL.
+Custom URLs: pick `custom` in TUI Preferences (or the first-run wizard), or pass a URL to the axis key directly.
 
 ## Why skit exists
 

{skit_cli-0.2.0 → skit_cli-0.3.0}/README.md

@@ -11,9 +11,9 @@
 
 **English** | [繁體中文](./README.zh-TW.md) | [简体中文](./README.zh-CN.md)
 
-**skit is a launcher and a home for your Python scripts.**
+**skit is a launcher and a home for your scripts.**
 
-skit stores your Python scripts in one place and makes them painless to launch.
+skit stores your scripts in one place and makes them painless to launch.
 
 **AI writes the scripts. skit gives them a home.**
 
@@ -25,19 +25,21 @@ script, and (with your OK) saving the good ones back, so they outlive the chat.
 
 ## What it does
 
-- **One home for your scripts.** `skit add` collects scattered scripts into a searchable library — keep a copy in the library, or reference the original file.
-- **Parameters without the pain.** Flags, `input()` calls, and the constants you tick become form fields (choices → pickers, booleans → checkboxes, types enforced).
+- **One home for your scripts and prompts.** `skit add` collects scattered scripts and prompts into a searchable library — keep a copy in the library, or reference the original file. Run it bare and it asks what you're adding; hand it a file it can't classify and it asks which kind, instead of erroring out.
+- **Parameters without the pain.** Flags, `input()` calls, and the constants you tick become form fields (choices → pickers, booleans → checkboxes, paths → completion and a file browser, types enforced).
+- **Paths you don't have to type.** Path fields complete as you type — press `→` to accept the suggestion — and `Ctrl+T` → *File or folder…* opens a browsable picker, so you never hand-type a directory again.
 - **It remembers.** Last-used values come back automatically; save favorites as named presets. Parameters marked secret never touch disk. Tokens like `{cwd}` and `{today}` keep presets portable.
-- **No environment mess.** skit declares each script's dependencies in the script itself (PEP 723) and runs it through uv in an isolated, cached environment — no venvs to manage, nothing installed globally.
+- **No environment mess.** Python scripts declare their dependencies inline (PEP 723) and run via uv in isolated environments; JS/TS scripts get a per-script `node_modules`, installed from their declared packages on first run. Nothing global either way. Other languages use the tools already on your machine — skit checks that declared external commands are on your `PATH` before running.
 - **Mouse or keyboard.** Plain `skit` opens the full TUI; every key hint on screen is also a clickable button.
 - **Automation-ready.** Every TUI action is also a CLI command with `--json` output and meaningful exit codes — for shell scripts, CI, and AI agents.
-- **Your agent's script library too.** The official [Agent Skill](https://agentskills.io) teaches Claude Code, Codex, Cursor, Gemini CLI, and friends the whole drill: discover scripts with `skit list`, read a parameter schema with `skit show`, run with `skit run --set … --no-input`. One `skit agent install` away — see [Works with your AI agent](#works-with-your-ai-agent).
+- **Prompts are first-class library entries.** Store a parameterized prompt (managed `{{placeholders}}` become form fields) and fire it at your coding agent — claude, codex, opencode, and friends are preconfigured runners, and any CLI is one `skit runner add` away.
+- **Your agent's library too.** The official [Agent Skill](https://agentskills.io) teaches Claude Code, Codex, Cursor, Gemini CLI, and friends the whole drill: discover entries with `skit list`, read a parameter schema with `skit show`, run with `skit run --set … --no-input`. One `skit agent install` away — see [Works with your AI agent](#works-with-your-ai-agent).
 - **Speaks your language.** English, 繁體中文, and 简体中文, with more to come. See [Languages](#languages).
 
 | Problem | What skit does |
 | --- | --- |
 | Scripts scattered all over the place | One central menu, with search |
-| Scripts with weird external dependencies | An isolated environment per script — dependencies declared in the file (PEP 723), resolved by uv |
+| Scripts that need specific packages or tools | Per-script dependencies for Python (PEP 723 + uv) and JS/TS (npm); for any language, skit checks declared external commands on your `PATH` |
 | CLI flags you forget ten minutes later, `input()` prompts, hard-coded constants meant to be edited by hand | Static analysis extracts them all into an interactive form — no code changes. Last-used values come prefilled; favorites save as presets. |
 | The weird script an AI wrote for you dies with the chat session | Agents check the library first, reuse what's there, and save the keepers — one-off scripts become permanent, parameterized tools |
 
@@ -54,6 +56,34 @@ Nothing to set up per script — no refactoring, no config to maintain. The scri
   <em>Fully mouse operable — every key hint on screen is also a button.</em>
 </p>
 
+## Language support
+
+Python, shell, and JS/TS get static parameter detection **and** value injection. The rest launch out of the box, accept declared parameters, and work with their own CLI parsers.
+
+| Kind | Runs via | Params detected | Injection | Reads its own CLI | Deps / needs |
+| --- | --- | --- | --- | --- | --- |
+| **Python** | `uv run --script` | constants, `input()` | ✅ | argparse · click · typer | PEP 723 (uv) + needs |
+| **Shell** (bash/sh/zsh) | interpreter | constants, `${VAR:-}` env-defaults, `read` | ✅ | getopts | needs |
+| **JS / TS** | deno › bun › node | `const` | ✅ | `util.parseArgs` | npm (per script) + needs |
+| **fish** | fish | `set -q NAME; or set NAME …` env-defaults | — | `argparse` builtin | needs |
+| **PowerShell** | pwsh | — | — | `param()` | needs |
+| **Ruby · Perl · Lua · R** | interpreter | — | — | — | needs |
+| **Programs** (exe) | direct exec | — | — | — | needs |
+| **Commands** | template fill | — | — | — | needs |
+| **Prompts** | your agent CLI (claude · codex · …) | `{{name}}` placeholders | — | — | needs |
+
+You can also declare parameters by hand for any kind — so even plain executables and command templates get the same form / preset / `--set` experience. **needs** are external commands — skit checks they're on your `PATH` before each run (any kind). Python and JS/TS get isolated per-script package dependencies: uv resolves the PEP 723 block, and npm-style deps install into a `node_modules` next to the stored copy (`skit add` suggests them from the script's own imports). Managed JS/TS deps apply to copied entries — a referenced script keeps using its own project's `node_modules` — and installs never run package lifecycle scripts (npm and bun get `--ignore-scripts`; deno skips them by default). One more evener: when deno is the runner skit picks, it passes `--allow-all`, so the same script behaves the same under deno, bun, and node. skit bootstraps uv for Python, but never a JS runtime — you supply node, bun, or deno.
+
+### Prompts
+
+A prompt entry is a reusable, parameterized piece of text for an AI coding agent. Add a `.prompt.md` file (or draft one with `skit add --prompt`); in interactive add review, choose which detected `{{placeholders}}` become form fields. Up to 30 are selected by default; when detection exceeds 30, none are selected by default, so code samples are not mistaken for variables. Managed fields get the full preset / last-values / `--set` experience. There are no escape sequences to learn: anything that isn't a placeholder you manage — unmanaged `{{holes}}` included — travels to the agent byte-for-byte as written, and a per-prompt switch (`--no-interpolate`, or one checkbox in Entry settings) turns insertion off entirely for prompts that were never written with it in mind. Running one renders the text and invokes the selected runner's configured argv command with it. The bundled Claude, Codex, OpenCode, and Antigravity commands open their interactive sessions; Amp is the deliberate exception, using its official `amp -x` one-shot mode to execute the prompt and return. The **runner** is picked on the run form (or pinned per prompt), claude / codex / opencode / amp / antigravity come preconfigured, and `skit runner add mycli -- mycli run {{prompt}}` registers anything else. The rendered prompt travels as a single process argument — no shell in between. One honest caveat: prompts are not a secrets channel — whatever the rendered text contains ends up in the receiving agent's own session logs.
+
+```bash
+skit add review.prompt.md            # managed placeholders become form fields
+skit run review                      # pick the agent, fill the form, go
+skit run review --runner codex --set target=src/app.py --no-input
+```
+
 ## Install
 
 skit is built on [uv](https://docs.astral.sh/uv/) (tested against 0.11.26). Don't have it? skit asks first, then downloads a pinned uv into its own private directory — your `PATH` and global environment stay untouched. A system-wide [install](https://docs.astral.sh/uv/getting-started/installation/) is still preferred.
@@ -101,7 +131,7 @@ That removes skit and its `PATH` shim. Your library and settings live **outside*
 | **Linux** | `~/.local/share/skit` · `~/.local/state/skit` · `~/.config/skit` |
 | **Windows** | `%LOCALAPPDATA%\skit` |
 
-They hold your script library, config, presets, and last-used values — plus, if skit ever bootstrapped its own uv, the private `uv` binary (in `…/skit/bin`, deleted along with the rest).
+They hold your tool library, config, presets, and last-used values — plus, if skit ever bootstrapped its own uv, the private `uv` binary (in `…/skit/bin`, deleted along with the rest).
 
 ```bash
 # macOS
@@ -124,6 +154,7 @@ Two commands are the whole interface:
 
 ```bash
 skit add my_script.py   # add a script
+skit add                # not sure what you're adding? it asks
 skit                    # open the menu, pick it, fill in the form, run
 ```
 
@@ -137,6 +168,7 @@ skit run my_script --dry-run  # print the exact command, don't run it
 skit run my_script --set width=800 --no-input   # set values explicitly, never prompt
 skit show my_script --json    # one script's full parameter schema, machine-readable
 skit params my_script         # show managed parameters and last-used values
+skit deps my_script --dep "requests>=2"   # set a script's package dependencies
 skit list --json              # machine-readable listing
 skit config                   # settings: language, editor, mirror, form style
 skit --help                   # everything else
@@ -169,18 +201,23 @@ skit follows your system language; switch it in the TUI preferences (for automat
 
 ## Mainland China (中国大陆)
 
-Three downloads tend to fail in mainland China: PyPI packages, the Python builds uv fetches from GitHub, and skit's own uv bootstrap. skit can route all three through domestic mirrors.
+Four downloads tend to fail in mainland China: PyPI packages, npm packages, the Python builds uv fetches from GitHub, and skit's own uv bootstrap. skit can route all four through domestic mirrors.
+
+Mirror settings live inside skit only: your global uv config is never touched, and existing mirror settings (`UV_DEFAULT_INDEX`, `uv.toml`, …) are respected. The npm registry rides `NPM_CONFIG_REGISTRY`: an existing value of that variable in your environment still wins, but note npm itself ranks it above `~/.npmrc`.
 
-Mirror settings live inside skit only: your global uv config is never touched, and existing mirror settings (`UV_DEFAULT_INDEX`, `uv.toml`, …) are respected.
+Each ecosystem is its own, independent choice — mirror vendors differ per ecosystem, so no single vendor name spans them:
 
-- **First run**: if PyPI/GitHub look unreachable, skit offers to turn mirrors on — just press Enter.
-- **Any time**: TUI Preferences → mirror, or:
+- **First run**: if PyPI/GitHub look unreachable, skit offers mirror setup — one question per ecosystem, Enter accepts each one's recommended preset.
+- **Any time**: TUI Preferences → mirrors, or:
 
 ```bash
-skit config mirror tsinghua   # or: aliyun / ustc / custom / off
+skit config mirror.pypi tsinghua    # Python packages: tsinghua / aliyun / ustc / a URL / off
+skit config mirror.github nju       # Python builds + the uv binary: nju / an https:// base URL / off
+skit config mirror.npm npmmirror    # JS/TS packages: npmmirror / a URL / off
+skit config mirror off              # master switch: off keeps the URLs; `on` restores them
 ```
 
-Defaults: PyPI via Tsinghua / Aliyun / USTC; Python builds and the uv binary via NJU. Pick `custom` to swap any URL.
+Custom URLs: pick `custom` in TUI Preferences (or the first-run wizard), or pass a URL to the axis key directly.
 
 ## Why skit exists
 

{skit_cli-0.2.0 → skit_cli-0.3.0}/pyproject.toml

@@ -2,8 +2,8 @@
 # Distribution name only ("skit" is admin-prohibited on PyPI); the import package,
 # CLI command, and config dirs all stay "skit".
 name = "skit-cli"
-version = "0.2.0"
-description = "Script launcher and parameter manager: all your scripts in one menu, their flags, input() calls, and constants auto-extracted into a run form — no more opening an IDE just to tweak a value."
+version = "0.3.0"
+description = "Launcher and parameter manager for scripts, prompts, programs, and commands: one library, one run form, nothing to memorize."
 readme = "README.md"
 requires-python = ">=3.12"
 license = "MIT"
@@ -19,6 +19,7 @@ keywords = [
     "script-runner",
     "automation",
     "ai-agent",
+    "ai-prompt",
     "agent-skills",
 ]
 classifiers = [
@@ -39,9 +40,14 @@ classifiers = [
 dependencies = [
     "typer>=0.26,<1",
     "platformdirs>=4.10,<5",
+    "packaging>=24,<27",
     "tomli-w>=1.2,<2",
     "textual>=8.2,<9",
     "rich>=15,<16",
+    "tree-sitter>=0.25,<0.27",
+    "tree-sitter-bash>=0.25,<0.26",
+    "tree-sitter-javascript>=0.25,<0.26",
+    "tree-sitter-typescript>=0.23,<0.24",
 ]
 
 [project.urls]
@@ -62,6 +68,7 @@ dev = [
     "mutmut>=3.6,<4",
     "zizmor>=1.26,<2",
     "babel>=2.18,<3",  # dev-only: extract/update/compile .po↔.mo (runtime uses stdlib gettext)
+    "pytest-rerunfailures>=16.4",
 ]
 
 [build-system]
@@ -190,4 +197,27 @@ source_paths = ["src/skit/"]
 pytest_add_cli_args_test_selection = ["tests/"]
 # The skill-sync test (tests/test_agent_skill.py) compares the repo-root skill against
 # the packaged copy; mutmut's mutants/ tree only carries src/ + tests/ by default.
-also_copy = ["skills/"]
+# README.md rides along because pyproject's `readme` references it — without it, uv
+# can't build the project inside mutants/ on a cold cache. scripts/ rides along because
+# the i18n-gate tests (test_js_deps.py) import scripts/i18n_coverage.py by path. locales/
+# must be explicit too: mutmut never refreshes non-Python files already present under a
+# reused source_paths copy, while also_copy directories are overlaid on every run. That
+# applies to both runtime package-data trees: translation catalogs and the bundled skill.
+also_copy = [
+    "skills/",
+    "README.md",
+    "scripts/",
+    "src/skit/locales/",
+    "src/skit/skills/",
+]
+# mutmut's native pragma scan only sees statement-level comments: a trailing pragma on a
+# multi-line statement marks the first line only, so an equivalent mutant on a later line
+# of the same statement can't be pinned natively. This pattern makes any line that carries
+# the pragma text skip the expression starting there, so a pragma can sit exactly on the
+# equivalent-mutant line (e.g. one branch of a wrapped ternary) without silencing its
+# siblings — mutants on the statement's other lines stay live. (Note the anchor is the
+# expression's FIRST line: call-argument mutants belong to the whole Call node, so they
+# can't be pinned per-argument this way — kill those with a forwarding test instead.) No
+# existing pragma line opens a multi-line expression, so for every other site this is a
+# no-op.
+do_not_mutate_patterns = ['pragma: no mutate']

{skit_cli-0.2.0 → skit_cli-0.3.0}/src/skit/agentskill.py

@@ -51,9 +51,14 @@ def default_roots() -> tuple[Path, Path]:
 def skill_text() -> str:
     """The bundled SKILL.md, read from the installed package (single source: the repo's
     skills/skit/SKILL.md is a test-enforced byte-identical copy of this file)."""
-    res = resources.files("skit").joinpath("skills", SKILL_DIR_NAME, SKILL_FILE_NAME)
+    package = "skit"
+    # files(None) infers this module's own package, and agentskill lives directly in `skit`, so
+    # anchor→None resolves to the identical package root — an equivalent mutant. Scoped to this one
+    # line so the killable anchor-string ("skit"→…) and joinpath mutants below stay mutation-tested.
+    root = resources.files(package)  # pragma: no mutate
+    res = root.joinpath("skills", SKILL_DIR_NAME, SKILL_FILE_NAME)
     # I/O kwarg mutants ("utf-8"→"UTF-8"/None) are equivalent aliases here; content is
-    # pinned by test_skill_text_is_the_bundled_skill (see docs/mutation-ledger.md).
+    # pinned by test_skill_ships_inside_the_package (see docs/mutation-ledger.md).
     return res.read_text(encoding="utf-8")  # pragma: no mutate