splitsym

Extract comments and split symbols from source files. Use when users want to extract inline comments, docstrings, or block comments from code files to unders...

Security Scan

The skill's code, docs, and runtime instructions are coherent with its stated purpose (extracting comments/docstrings) and it does not request credentials, install anything, or perform network/executable actions.

Purpose & Capability

Name/description match the shipped files: splitsym.py implements a comment/docstring extractor and symbols.json contains the extraction rules. There are no unrelated env vars, binaries, or cloud credentials requested.

Instruction Scope

SKILL.md instructs running the tool against a file and (optionally) a config; the implementation only reads the target file and a local config and prints comment snippets. It does not read other system files, environment variables, or send data to external endpoints.

Install Mechanism

This is an instruction-only/standalone Python script with no install spec. There is no remote download, package install, or archive extraction specified in the metadata.

Credentials

No environment variables, credentials, or config paths beyond a user-provided config file (~/.config/splitsym/symbols.json) are required. The default config location is reasonable for a CLI tool and is not excessive.

Persistence & Privilege

The skill does not request persistent/always-on presence and does not modify other skills or global agent settings. It runs only when invoked.

Assessment

This skill appears to do what it says: it reads the target source file and a local symbols.json to extract comments/docstrings and prints snippets. It does not contact the network or request secrets. Two practical notes before installing or running: (1) the tool expects a config at ~/.config/splitsym/symbols.json by default — either create that file or invoke with --config pointing to the included symbols.json, and (2) the config contains regex patterns: only use/trust configs from sources you control because malicious or pathological regexes could cause unexpected behavior or processing delays on very large files.

splitsym

Extract split symbols (line or pair) from source files. Analyzes source code and extracts comments based on file type.

Usage

splitsym <file> [--lines M-N] [--config CONFIG]

Arguments

Argument	Description
file	Source file to analyze (required)
--lines	Optional line range (e.g., 100-200)
--config	Path to symbols.json config (default: ~/.config/splitsym/symbols.json)

Supported File Types

Extension	Comment Style
.py, .rb, .sh, .yaml	# comment
.c, .js, .ts, .java	// comment
.sql, .hs	-- comment
.lisp, .clj	; comment
.tex, .erl	% comment
.html, .xml, .vue	<!-- comment -->
.py	"""docstring""" or '''docstring'''
.ml, .mli	(* comment *)

Example

# Extract all comments from a Python file
splitsym myfile.py

# Extract comments from specific line range
splitsym myfile.py --lines 100-200

# Use custom config
splitsym myfile.py --config ./my-symbols.json

Output Format

   123      PAIR: multi-line comment content...
     45    # This is a comment line

• Line numbers are right-aligned (6 digits)
• Indentation is preserved
• PAIR: prefix indicates multi-line block comments