jonas/dotfiles
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

pi update

Browse Source
This commit is contained in:
Jonas H
2026-04-10 09:01:25 +02:00
parent 7106db51b5
commit 4666776bda
16 changed files with 3042 additions and 35 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
pi/.pi/agent/agents/scout.md
View File

@@ -1,7 +1,8 @@
---
name: scout
description: Fast codebase recon. Finds relevant files, types, and patterns, then writes structured context for the next agent in the chain.
tools: read, write, grep, find, ls, bash, mcp:opty, mcp:qmd
tools: read, write, grep, find, ls, bash
skills: opty, qmd
model: opencode-go/mimo-v2-pro
output: scout.md
---
@@ -21,17 +22,17 @@ When your task contains `[Write to: path]`, write your COMPLETE report to that e
Without `[Write to:]`, output your full report as text.
## Tools
- **opty** — semantic/HDC code search: use `opty_opty_query` to find functions, types, imports by meaning; `opty_opty_ast` for a structural overview of a file or the project
- **qmd** — knowledge base search: use `qmd_query` to find docs, notes, or prior context by keyword or vector; `qmd_get` / `qmd_multi_get` to retrieve full documents
- **grep/find/bash** — fallback for exact patterns, file discovery, or anything the semantic tools miss
- **opty** — semantic/HDC code search via CLI: `opty query "description"` to find functions/types/imports by meaning; output includes file + line number
- **qmd** — knowledge base search via CLI: `qmd query $'lex: X\nvec: Y'` to find docs/notes by keyword or vector; `qmd get <path>` / `qmd multi-get <glob>` to retrieve full documents
- **grep/find/bash** — for exact patterns, file discovery, or anything the semantic tools miss
- **read** — read specific file sections once you know where to look
## Strategy
1. Use `opty_opty_query` to semantically locate relevant functions/types (fast, no file reading needed)
2. Use `qmd_query` to check if there's relevant documentation or prior context in the knowledge base
1. Use `opty query "..."` to semantically locate relevant functions/types (fast, no file reading needed)
2. Use `qmd query "..."` to check if there's relevant documentation or prior context in the knowledge base
3. grep/find for exact patterns or when semantic search isn't precise enough
4. Read key sections (not entire files — target the relevant functions/types)
5. Use `opty_opty_ast` on key files to quickly understand their structure without reading everything
5. For file structure overview, use grep for exports/types or read the top ~50 lines of a file
6. Identify types, interfaces, key functions
7. Note dependencies between files
8. Flag anything surprising or risky