summaryrefslogtreecommitdiff
path: root/prompts/skills/next-task
diff options
context:
space:
mode:
authorPaul Buetow <paul@buetow.org>2026-05-27 20:22:39 +0300
committerPaul Buetow <paul@buetow.org>2026-05-27 20:22:39 +0300
commit387ae1e8dece4d890a4221099de841d2fda158a7 (patch)
tree3fc28c126344591873cd5289648e62b140871ef9 /prompts/skills/next-task
parent409b07bfe3bc950d195b38341f4bc034fa1c9256 (diff)
update prompts
Diffstat (limited to 'prompts/skills/next-task')
-rw-r--r--prompts/skills/next-task/SKILL.md7
1 files changed, 3 insertions, 4 deletions
diff --git a/prompts/skills/next-task/SKILL.md b/prompts/skills/next-task/SKILL.md
index cb87950..0677212 100644
--- a/prompts/skills/next-task/SKILL.md
+++ b/prompts/skills/next-task/SKILL.md
@@ -26,14 +26,13 @@ Find the highest-priority agent task to work on next, switch to the right projec
- Prefer the first project whose directory exists under `~/git/`; otherwise pick the first project listed.
3. **Switch to the target project's git repository.**
- - The repository lives somewhere under `~/git/`. It may be at the top level (`~/git/<project>`) or nested in a sub-directory (e.g. `~/git/work/<project>`, `~/git/forks/<project>`). Always do a depth-3 search across all of `~/git/`:
+ - The project directory is always `~/git/<project>` — a flat layout, no nesting. Check that path first:
```sh
- find ~/git -maxdepth 3 -type d -name '<project>' -exec test -e {}/.git \; -print
+ test -d ~/git/<project>/.git && echo exists
```
- If that returns nothing, retry with `-iname '<project>'` for a case-insensitive match. As a last resort, allow simple suffix/prefix differences (e.g. project `ior` → directory `ior-go`).
- - If multiple candidates match, prefer (in order): exact name containing `.git`, shallowest path, then ask the user.
+ If that directory does not exist, retry with a case-insensitive match or simple suffix/prefix differences (e.g. project `ior` → directory `ior-go`) before asking the user.
- If nothing plausible is found, stop and ask the user which repo to use.
- Use the `cwd` parameter of subsequent tool calls to operate inside that repository. Do **not** chain `cd` with `&&` in tool calls — pass `cwd` instead.