From bb4d218fb4c180d02e0d1456897ef5b592f9bc2a Mon Sep 17 00:00:00 2001 From: mathjams Date: Wed, 3 Jun 2026 19:08:56 +0000 Subject: [PATCH 1/3] use-probe: prefer probe before grep/find sweeps; broaden skill trigger --- plugins/probe/skills/use-probe/SKILL.md | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-) diff --git a/plugins/probe/skills/use-probe/SKILL.md b/plugins/probe/skills/use-probe/SKILL.md index 530a5d1..3df0d5b 100644 --- a/plugins/probe/skills/use-probe/SKILL.md +++ b/plugins/probe/skills/use-probe/SKILL.md @@ -1,14 +1,18 @@ --- name: use-probe -description: Use probe_search and probe_read to search indexed project docs and code before broad grep/read sweeps. Use for repository architecture, implementation details, APIs, setup flows, design docs, runbooks, or questions about where behavior is defined. +description: Prefer probe_search/probe_read for code and docs exploration — finding definitions, call sites, usages, config, or where behavior lives. Reach for it before a grep/find/glob sweep when locating code in an unfamiliar repo, not only for direct "where is X" questions. --- # Use probe -Use probe as the first pass when the user asks about project knowledge that may span files, docs, or code. +Use probe as your default first step for code and documentation discovery. Prefer it over +grep/find/glob when you need to locate something in an unfamiliar repo; switch to raw file +tools once probe has pointed you to the right place. -1. Start with `probe_search` before broad `grep`, `find`, or reading many files. -2. Ask focused natural-language queries. Prefer one or two targeted searches over a vague sweep. +1. Start with `probe_search` before a broad `grep`/`find`/`glob` or reading several files — + to locate definitions, call sites, usages, config, and where behavior lives. +2. Ask focused natural-language queries; run a few targeted searches as the task evolves + rather than one vague sweep. 3. Check the `refreshed` field in `probe_search`. If it contains an error, say the search used the last good local index. 4. Prefer focused `probe_read(file_path, line_start, line_end, context_lines=...)` calls when search returns line ranges and you need more context. @@ -16,4 +20,5 @@ Use probe as the first pass when the user asks about project knowledge that may 6. Use normal file tools after probe narrows the search, especially for exact line checks or edits. 7. Run `probe_index` only when the user asks, search is empty, or freshness looks wrong. -Do not use probe for a file the user already named unless repo context or related docs would help. +Don't force probe for a file you've already been pointed to, but lean on it whenever you're +searching for code you haven't located yet. From 9c621197504abf1c0cebd25696f8012c90d9fdb9 Mon Sep 17 00:00:00 2001 From: mathjams Date: Wed, 3 Jun 2026 19:10:39 +0000 Subject: [PATCH 2/3] use-probe (codex): same prefer-probe-before-grep wording --- plugins/probe-codex/skills/use-probe/SKILL.md | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-) diff --git a/plugins/probe-codex/skills/use-probe/SKILL.md b/plugins/probe-codex/skills/use-probe/SKILL.md index 530a5d1..3df0d5b 100644 --- a/plugins/probe-codex/skills/use-probe/SKILL.md +++ b/plugins/probe-codex/skills/use-probe/SKILL.md @@ -1,14 +1,18 @@ --- name: use-probe -description: Use probe_search and probe_read to search indexed project docs and code before broad grep/read sweeps. Use for repository architecture, implementation details, APIs, setup flows, design docs, runbooks, or questions about where behavior is defined. +description: Prefer probe_search/probe_read for code and docs exploration — finding definitions, call sites, usages, config, or where behavior lives. Reach for it before a grep/find/glob sweep when locating code in an unfamiliar repo, not only for direct "where is X" questions. --- # Use probe -Use probe as the first pass when the user asks about project knowledge that may span files, docs, or code. +Use probe as your default first step for code and documentation discovery. Prefer it over +grep/find/glob when you need to locate something in an unfamiliar repo; switch to raw file +tools once probe has pointed you to the right place. -1. Start with `probe_search` before broad `grep`, `find`, or reading many files. -2. Ask focused natural-language queries. Prefer one or two targeted searches over a vague sweep. +1. Start with `probe_search` before a broad `grep`/`find`/`glob` or reading several files — + to locate definitions, call sites, usages, config, and where behavior lives. +2. Ask focused natural-language queries; run a few targeted searches as the task evolves + rather than one vague sweep. 3. Check the `refreshed` field in `probe_search`. If it contains an error, say the search used the last good local index. 4. Prefer focused `probe_read(file_path, line_start, line_end, context_lines=...)` calls when search returns line ranges and you need more context. @@ -16,4 +20,5 @@ Use probe as the first pass when the user asks about project knowledge that may 6. Use normal file tools after probe narrows the search, especially for exact line checks or edits. 7. Run `probe_index` only when the user asks, search is empty, or freshness looks wrong. -Do not use probe for a file the user already named unless repo context or related docs would help. +Don't force probe for a file you've already been pointed to, but lean on it whenever you're +searching for code you haven't located yet. From a0f3c755b5a2b0ea1e6baac5cff7e48566e72d86 Mon Sep 17 00:00:00 2001 From: mathjams Date: Wed, 3 Jun 2026 19:13:36 +0000 Subject: [PATCH 3/3] use-probe: keep 'architecture' in description (satisfy skill test) --- plugins/probe-codex/skills/use-probe/SKILL.md | 2 +- plugins/probe/skills/use-probe/SKILL.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/plugins/probe-codex/skills/use-probe/SKILL.md b/plugins/probe-codex/skills/use-probe/SKILL.md index 3df0d5b..b589921 100644 --- a/plugins/probe-codex/skills/use-probe/SKILL.md +++ b/plugins/probe-codex/skills/use-probe/SKILL.md @@ -1,6 +1,6 @@ --- name: use-probe -description: Prefer probe_search/probe_read for code and docs exploration — finding definitions, call sites, usages, config, or where behavior lives. Reach for it before a grep/find/glob sweep when locating code in an unfamiliar repo, not only for direct "where is X" questions. +description: Prefer probe_search/probe_read for code and docs exploration — finding definitions, call sites, usages, config, architecture, or where behavior lives. Reach for it before a grep/find/glob sweep when locating code in an unfamiliar repo, not only for direct "where is X" questions. --- # Use probe diff --git a/plugins/probe/skills/use-probe/SKILL.md b/plugins/probe/skills/use-probe/SKILL.md index 3df0d5b..b589921 100644 --- a/plugins/probe/skills/use-probe/SKILL.md +++ b/plugins/probe/skills/use-probe/SKILL.md @@ -1,6 +1,6 @@ --- name: use-probe -description: Prefer probe_search/probe_read for code and docs exploration — finding definitions, call sites, usages, config, or where behavior lives. Reach for it before a grep/find/glob sweep when locating code in an unfamiliar repo, not only for direct "where is X" questions. +description: Prefer probe_search/probe_read for code and docs exploration — finding definitions, call sites, usages, config, architecture, or where behavior lives. Reach for it before a grep/find/glob sweep when locating code in an unfamiliar repo, not only for direct "where is X" questions. --- # Use probe