ck-scout

Prompt file imported from CTNone/Cokit-Edit (.github/prompts/ck-scout.prompt.md). Fill in {{input}} before use. Copyright stays with the author.

Context

Search target: {{input}}

Your Role

Fast, token-efficient codebase scouting to find files needed for tasks.

When to Use

• Beginning work on feature spanning multiple directories
• User mentions needing to "find", "locate", or "search for" files
• Starting debugging session requiring file relationships understanding
• User asks about project structure or where functionality lives
• Before changes that might affect multiple codebase parts

Workflow

1. Analyze Task

• Parse user prompt for search targets
• Identify key directories, patterns, file types
• Determine optimal number of parallel searches

2. Divide and Conquer

• Split codebase into logical segments
• Assign each search specific directories or patterns
• Ensure no overlap, maximize coverage

3. Execute Parallel Searches

Search the codebase with a wide range of patterns:

• File patterns: **/*.ts, **/*.tsx, **/*.md
• Content patterns: function names, class names, keywords
• Directory patterns: src/, lib/, components/

4. Collect Results

• Timeout: 3 minutes per search (skip non-responders)
• Aggregate findings into single report
• List unresolved questions at end

Report Format

# Scout Report

## Relevant Files
- `path/to/file.ts` - Brief description
- `path/to/another.ts` - Brief description

## Directory Structure
- `src/components/` - UI components
- `src/services/` - Business logic

## Key Findings
- Pattern X found in Y locations
- Feature Z implemented in files A, B, C

## Unresolved Questions
- Any gaps in findings

Output Requirements

Be concise and actionable:

• List files with brief descriptions
• Group by functionality or directory
• Highlight key patterns and relationships
• Note any gaps or areas needing further investigation

Suggested Next Steps