think-in-code

Aggregates multi-file audits into single Bash pipelines instead of sequential Read calls.

1|Updated Jul 29, 2026
One-click install
npx skills add https://github.com/fusengine/kimi-code --skill think-in-code-fusengine
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: think-in-code
Source: https://github.com/fusengine/kimi-code/tree/main/plugins/ai-pilot/skills/think-in-code
Command: npx skills add https://github.com/fusengine/kimi-code --skill think-in-code-fusengine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reading many files one by one to extract summaries wastes context tokens and slows down codebase analysis. This Skill replaces N sequential Read calls with one compact shell pipeline that returns only the aggregated result you need. ## Core Features & Use Cases - File Size Audits: Find files exceeding line-count thresholds (e.g., > 100 lines) across TypeScript, Python, and PHP codebases with a single find/wc/awk pipeline. - Symbol and Dependency Extraction: Grep exported symbols as compact JSON via ripgrep and jq, or list package dependencies with versions from package.json and composer.json. - Log and LOC Scanning: Scan error logs for ERROR/FATAL patterns and compute lines-of-code breakdowns by file extension. - Use Case: When asked to find all files over 100 lines in src/, run one find | xargs wc -l | awk pipeline and get a ~1KB sorted table instead of consuming ~60KB reading ten files individually. ## Quick Start Ask the agent to audit the codebase for files over 100 lines using a single shell pipeline instead of reading files individually.

Frequently Asked Questions about think-in-code

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find files over 100 lines in a codebase?▼

Run a single pipeline: find with name filters for your extensions, pipe to xargs wc -l, then filter with awk '$1 > 100' and sort descending. This returns a compact sorted table without reading any file contents into context.

How to grep exported symbols across multiple TypeScript files?▼

Use ripgrep with --json output and a pattern like 'export (function|class|const)', then pipe through jq to extract path, line number, and matched text. This yields a compact list of symbols without opening each file.

When should I use Read instead of a shell pipeline?▼

Use Read only for targeted inspection of one specific file you already know matters. If the task is computing or extracting something per file and then aggregating, a shell pipeline is the correct choice.

Does this approach work for PHP and Python projects?▼

Yes, the pipelines include patterns for .php and .py files, excluding vendor and node_modules directories. Dependency listing supports composer.json for PHP and package.json for Node via jq.

Why is reading files sequentially to count lines wasteful?▼

Each Read loads full file contents into context, roughly 6KB per file, so ten files consume about 60KB for a result that fits in 1KB. A wc -l pipeline returns only the aggregated numbers, about a 60x token reduction.