btca-local

Search and aggregate results across local git repositories in a sandbox.

3.1k|528|Updated Apr 13, 2025
One-click install
npx skills add https://github.com/stickerdaniel/linkedin-mcp-server --skill btca-local
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: btca-local
Source: https://github.com/stickerdaniel/linkedin-mcp-server/tree/main/.agents/skills/btca-local
Command: npx skills add https://github.com/stickerdaniel/linkedin-mcp-server --skill btca-local

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

BTCA Local provides a simple mechanism to search code and resources across repositories cloned on the local machine, eliminating the need to manually grep through multiple folders.

Core Features & Use Cases

  • Local repo discovery and fast search across cloned repos
  • Deterministic workflow: load and update repos as needed
  • Guided, context-aware search across multiple repositories within a sandbox

Quick Start

Clone or update repos in ~/.btca/agent/sandbox, then run a search across the loaded repositories.

Frequently Asked Questions about btca-local

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

FAQPage Schema
How do I search code across multiple local git repositories at once?

To search code across local git repositories, clone or update them in the ~/.btca/agent/sandbox directory. The tool then aggregates file lookup and reference discovery results across all loaded repos.

What is the best way to find references in cloned git repos without manual grep?

Finding references in cloned git repos is handled by a deterministic workflow that loads and updates repositories on demand within a local sandbox, replacing manual grep with context-aware search results.

Can I search for files in a local sandbox if my repositories are not yet cloned?

Searching local repositories requires them to be cloned or updated in the ~/.btca/agent/sandbox folder first. The tool cannot search repositories that have not been loaded into this local sandbox.

Does local repository search work with deterministic workflows for code lookup?

Local repository search implements a deterministic workflow that loads, updates, and searches code according to user context. This ensures consistent and repeatable file lookup and reference discovery across repositories.

Why use a sandbox for searching local code instead of searching the entire machine?

Using a sandbox for searching local code confines the deterministic workflow to repositories within ~/.btca/agent/sandbox. This restriction enables fast, context-aware aggregation across multiple defined repositories rather than scanning the entire machine.