foxctl SWE Grep

Extract relevant code snippets from repository files using natural-language questions.

3|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/joshka0/foxctl --skill foxctl-swe-grep
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: foxctl SWE Grep
Source: https://github.com/joshka0/foxctl/tree/main/configs/skills/foxctl-swe-grep
Command: npx skills add https://github.com/joshka0/foxctl --skill foxctl-swe-grep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces the time it takes to find the most relevant code by automatically extracting high-signal snippets from a live codebase in response to natural-language questions.

Core Features & Use Cases

  • Smart code snippet extraction: Produces focused excerpts from candidate files, prioritizing what best answers your question.
  • Evidence-aware retrieval workflow: Works as the final stage after semantic/symbol indexes shortlist likely files, then pulls the necessary lines from the workspace.
  • Guided precision controls: Supports candidate priorities, optional symbol hints, and configurable limits (max files, max snippets, and max bytes per file) to keep results relevant and efficient.
  • Use cases: Use it to answer “how does X work?”, speed up bug investigations by locating relevant handlers and logic, and support feature planning by extracting existing patterns before changing the code.

Quick Start

Ask for targeted snippets by running foxctl on the snippet_extract stage with a workspace_id, your natural-language question, and a list of candidate file paths.

Frequently Asked Questions about foxctl SWE Grep

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

FAQPage Schema
How do I extract relevant code snippets from a repository using natural language?

You can extract code snippets by providing a workspace ID, a natural-language question, and candidate file paths to retrieve high-signal excerpts. The tool reads the live workspace and selects the most relevant lines matching your query.

What is evidence-aware code retrieval and when do I need it?

Evidence-aware code retrieval is a workflow where semantic or symbol indexes first shortlist likely files, then live workspace reading extracts the exact snippets. You need this approach when searching large codebases to answer how specific functions or handlers work.

Can I limit the number of files and bytes returned during code retrieval?

Yes, you can enforce configurable limits on max files, max snippets, and max bytes per file during code retrieval. These precision controls keep results relevant and efficient while prioritizing candidate files based on assigned priority levels.

How do I use symbol hints to improve code snippet extraction results?

Symbol hints improve code snippet extraction by providing optional symbol IDs alongside candidate paths. This guides the retrieval process to focus on specific functions or variables, ensuring extracted excerpts better answer your natural-language question.

Does semantic search alone work for finding how specific handlers work in a codebase?

Semantic search alone identifies candidate files but cannot extract exact code snippets. You need a final retrieval stage that reads the live workspace to pull the necessary lines, using optional symbol hints and priority levels for focused results.

What's the best way to locate existing code patterns before implementing a new feature?

The best way to locate existing code patterns is running snippet extraction with a natural-language question and candidate file paths. This pulls high-signal excerpts from the live workspace, revealing current patterns to guide feature planning and modifications.