incitaciones 0.10.3 → 0.10.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (5) hide show
  1. package/content/distilled/session/references/renew/SKILL.md +25 -23
  2. package/content/manifest.json +1 -1
  3. package/package.json +1 -1
  4. package/pi-package/skills/renew/SKILL.md +25 -23
  5. package/pi-package/skills/session/references/renew/SKILL.md +25 -23
package/content/distilled/session/references/renew/SKILL.md CHANGED
@@ -15,7 +15,20 @@ Uses `$JOURNAL_PATH` (defaults to `~/dev/status`) for the daily log journal, and
15
15
  cd "$JOURNAL" && git pull
16
16
  ```
17
17
 
18
- 2. Identify the target.
18
+ 2. **Decide the data source before any journal or whisper lookup.**
19
+
20
+ Run `turu key --json` once, right now. Its result governs everything below:
21
+
22
+ - **turu available:** `turu recall` is the primary source for recent
23
+ session history. Run `turu recall repo` and `turu recall branch` now,
24
+ and treat their output as superseding steps 5-6 — only fall back to
25
+ those log/inbox greps if recall returned nothing for this slug.
26
+ Never `ls`/`find` `~/.whisper/` to guess paths: canonical keys don't
27
+ match raw remote URLs.
28
+ - **turu absent:** proceed with the journal steps (3-6) and the
29
+ `~/.whisper/` fallback path lookup in step 8.
30
+
31
+ 3. Identify the target.
19
32
 
20
33
  **If a `<slug>` is provided:** The user says `/renew <slug>`.
21
34
 
@@ -32,41 +45,28 @@ Uses `$JOURNAL_PATH` (defaults to `~/dev/status`) for the daily log journal, and
32
45
  - If multiple matches found, list them and ask the user to pick
33
46
  - If no match found, list available projects/areas and ask
34
47
 
35
- 3. Read the matched project or area file.
48
+ 4. Read the matched project or area file.
36
49
 
37
- 4. Read today's log (`$JOURNAL/$LOG_SUBDIR/YYYY/YYYY-MM/YYYY-MM-DD.md`).
50
+ 5. Read today's log (`$JOURNAL/$LOG_SUBDIR/YYYY/YYYY-MM/YYYY-MM-DD.md`).
38
51
  If it doesn't exist, create it with the daily log template.
39
52
  Scan for any earlier session entries related to this project/area today.
40
53
 
41
- 5. Search recent logs for context (last 3 days):
54
+ 6. Search recent logs for context (last 3 days; skip when step 2's `turu recall branch` already surfaced the recent sessions):
42
55
  ```bash
43
56
  grep -rl "<slug>" "$JOURNAL"/"$LOG_SUBDIR"/YYYY/YYYY-MM/ 2>/dev/null | tail -3
44
57
  ```
45
58
  Read any matches to understand recent session history.
46
59
 
47
- 6. Search inbox for related items:
60
+ 7. Search inbox for related items (skip when `turu recall branch` already surfaced them):
48
61
  ```bash
49
62
  grep -i "<slug>" "$JOURNAL"/inbox.md
50
63
  ```
51
64
 
52
- 7. **Check for accumulated whisper knowledge.**
65
+ 8. **Load whisper knowledge** — only for the turu-absent branch of step 2
66
+ (when turu is available, `turu recall` already ran there; do not repeat
67
+ or hand-roll it):
53
68
 
54
- **If `turu` is available** (`turu key --json` succeeds), delegate every
55
- mechanical step to it — never hand-roll repo-key or path derivation:
56
- ```bash
57
- turu key --json # canonical repo key, branch slug, worktree slot
58
- turu recall repo # repo-scope knowledge (env facts)
59
- turu recall branch # branch-scope knowledge (notes)
60
- turu recall worktree # worktree-slot knowledge (only when step 8 uses one)
61
- ```
62
- - `turu recall` output already routes to the right store (global, repo,
63
- or repo-local `.whisper/`), so never `ls`/`find` `~/.whisper/` to guess
64
- paths — canonical keys don't match raw remote URLs.
65
- - `turu recall` exits non-zero with `nothing to recall in this scope`
66
- when a scope is empty — treat that as "no knowledge here", not a
67
- failure; move on without improvising alternate lookup paths.
68
-
69
- **Fallback (turu absent):** if `~/.whisper/` exists, load context with:
69
+ If `~/.whisper/` exists, load context with:
70
70
  ```bash
71
71
  repo_url=$(git remote get-url origin 2>/dev/null | sed 's|https://||;s|git@||;s|\.git$||')
72
72
  branch_slug=$(git rev-parse --abbrev-ref HEAD | sed 's|/|--|g')
@@ -87,7 +87,9 @@ Uses `$JOURNAL_PATH` (defaults to `~/dev/status`) for the daily log journal, and
87
87
  ```
88
88
  Surface any `in_progress` tickets prominently. The **Suggested next step** must only reference tickets NOT currently `in_progress`.
89
89
 
90
- 8. If the project/area has a worktree or repo path noted in its file, gather git context:
90
+ 9. If the project/area has a worktree or repo path noted in its file, gather git context:
91
+ - When turu is available and a worktree is actually used, also run
92
+ `turu recall worktree` for its slot knowledge.
91
93
  - `cd <worktree-path> && git branch --show-current`
92
94
  - `git log --oneline -5`
93
95
  - `git status --short`
package/content/manifest.json CHANGED
@@ -1,5 +1,5 @@
1
1
  {
2
- "version": "2026-09-18",
2
+ "version": "2026-09-28",
3
3
  "schema_version": "1.1",
4
4
  "prompts": [
5
5
  {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "incitaciones",
3
- "version": "0.10.3",
3
+ "version": "0.10.4",
4
4
  "description": "Reusable prompts and skills for CLI LLM tools, with native pi package support.",
5
5
  "repository": {
6
6
  "type": "git",
package/pi-package/skills/renew/SKILL.md CHANGED
@@ -29,7 +29,20 @@ Uses `$JOURNAL_PATH` (defaults to `~/dev/status`) for the daily log journal, and
29
29
  cd "$JOURNAL" && git pull
30
30
  ```
31
31
 
32
- 2. Identify the target.
32
+ 2. **Decide the data source before any journal or whisper lookup.**
33
+
34
+ Run `turu key --json` once, right now. Its result governs everything below:
35
+
36
+ - **turu available:** `turu recall` is the primary source for recent
37
+ session history. Run `turu recall repo` and `turu recall branch` now,
38
+ and treat their output as superseding steps 5-6 — only fall back to
39
+ those log/inbox greps if recall returned nothing for this slug.
40
+ Never `ls`/`find` `~/.whisper/` to guess paths: canonical keys don't
41
+ match raw remote URLs.
42
+ - **turu absent:** proceed with the journal steps (3-6) and the
43
+ `~/.whisper/` fallback path lookup in step 8.
44
+
45
+ 3. Identify the target.
33
46
 
34
47
  **If a `<slug>` is provided:** The user says `/renew <slug>`.
35
48
 
@@ -46,41 +59,28 @@ Uses `$JOURNAL_PATH` (defaults to `~/dev/status`) for the daily log journal, and
46
59
  - If multiple matches found, list them and ask the user to pick
47
60
  - If no match found, list available projects/areas and ask
48
61
 
49
- 3. Read the matched project or area file.
62
+ 4. Read the matched project or area file.
50
63
 
51
- 4. Read today's log (`$JOURNAL/$LOG_SUBDIR/YYYY/YYYY-MM/YYYY-MM-DD.md`).
64
+ 5. Read today's log (`$JOURNAL/$LOG_SUBDIR/YYYY/YYYY-MM/YYYY-MM-DD.md`).
52
65
  If it doesn't exist, create it with the daily log template.
53
66
  Scan for any earlier session entries related to this project/area today.
54
67
 
55
- 5. Search recent logs for context (last 3 days):
68
+ 6. Search recent logs for context (last 3 days; skip when step 2's `turu recall branch` already surfaced the recent sessions):
56
69
  ```bash
57
70
  grep -rl "<slug>" "$JOURNAL"/"$LOG_SUBDIR"/YYYY/YYYY-MM/ 2>/dev/null | tail -3
58
71
  ```
59
72
  Read any matches to understand recent session history.
60
73
 
61
- 6. Search inbox for related items:
74
+ 7. Search inbox for related items (skip when `turu recall branch` already surfaced them):
62
75
  ```bash
63
76
  grep -i "<slug>" "$JOURNAL"/inbox.md
64
77
  ```
65
78
 
66
- 7. **Check for accumulated whisper knowledge.**
79
+ 8. **Load whisper knowledge** — only for the turu-absent branch of step 2
80
+ (when turu is available, `turu recall` already ran there; do not repeat
81
+ or hand-roll it):
67
82
 
68
- **If `turu` is available** (`turu key --json` succeeds), delegate every
69
- mechanical step to it — never hand-roll repo-key or path derivation:
70
- ```bash
71
- turu key --json # canonical repo key, branch slug, worktree slot
72
- turu recall repo # repo-scope knowledge (env facts)
73
- turu recall branch # branch-scope knowledge (notes)
74
- turu recall worktree # worktree-slot knowledge (only when step 8 uses one)
75
- ```
76
- - `turu recall` output already routes to the right store (global, repo,
77
- or repo-local `.whisper/`), so never `ls`/`find` `~/.whisper/` to guess
78
- paths — canonical keys don't match raw remote URLs.
79
- - `turu recall` exits non-zero with `nothing to recall in this scope`
80
- when a scope is empty — treat that as "no knowledge here", not a
81
- failure; move on without improvising alternate lookup paths.
82
-
83
- **Fallback (turu absent):** if `~/.whisper/` exists, load context with:
83
+ If `~/.whisper/` exists, load context with:
84
84
  ```bash
85
85
  repo_url=$(git remote get-url origin 2>/dev/null | sed 's|https://||;s|git@||;s|\.git$||')
86
86
  branch_slug=$(git rev-parse --abbrev-ref HEAD | sed 's|/|--|g')
@@ -101,7 +101,9 @@ Uses `$JOURNAL_PATH` (defaults to `~/dev/status`) for the daily log journal, and
101
101
  ```
102
102
  Surface any `in_progress` tickets prominently. The **Suggested next step** must only reference tickets NOT currently `in_progress`.
103
103
 
104
- 8. If the project/area has a worktree or repo path noted in its file, gather git context:
104
+ 9. If the project/area has a worktree or repo path noted in its file, gather git context:
105
+ - When turu is available and a worktree is actually used, also run
106
+ `turu recall worktree` for its slot knowledge.
105
107
  - `cd <worktree-path> && git branch --show-current`
106
108
  - `git log --oneline -5`
107
109
  - `git status --short`
package/pi-package/skills/session/references/renew/SKILL.md CHANGED
@@ -15,7 +15,20 @@ Uses `$JOURNAL_PATH` (defaults to `~/dev/status`) for the daily log journal, and
15
15
  cd "$JOURNAL" && git pull
16
16
  ```
17
17
 
18
- 2. Identify the target.
18
+ 2. **Decide the data source before any journal or whisper lookup.**
19
+
20
+ Run `turu key --json` once, right now. Its result governs everything below:
21
+
22
+ - **turu available:** `turu recall` is the primary source for recent
23
+ session history. Run `turu recall repo` and `turu recall branch` now,
24
+ and treat their output as superseding steps 5-6 — only fall back to
25
+ those log/inbox greps if recall returned nothing for this slug.
26
+ Never `ls`/`find` `~/.whisper/` to guess paths: canonical keys don't
27
+ match raw remote URLs.
28
+ - **turu absent:** proceed with the journal steps (3-6) and the
29
+ `~/.whisper/` fallback path lookup in step 8.
30
+
31
+ 3. Identify the target.
19
32
 
20
33
  **If a `<slug>` is provided:** The user says `/renew <slug>`.
21
34
 
@@ -32,41 +45,28 @@ Uses `$JOURNAL_PATH` (defaults to `~/dev/status`) for the daily log journal, and
32
45
  - If multiple matches found, list them and ask the user to pick
33
46
  - If no match found, list available projects/areas and ask
34
47
 
35
- 3. Read the matched project or area file.
48
+ 4. Read the matched project or area file.
36
49
 
37
- 4. Read today's log (`$JOURNAL/$LOG_SUBDIR/YYYY/YYYY-MM/YYYY-MM-DD.md`).
50
+ 5. Read today's log (`$JOURNAL/$LOG_SUBDIR/YYYY/YYYY-MM/YYYY-MM-DD.md`).
38
51
  If it doesn't exist, create it with the daily log template.
39
52
  Scan for any earlier session entries related to this project/area today.
40
53
 
41
- 5. Search recent logs for context (last 3 days):
54
+ 6. Search recent logs for context (last 3 days; skip when step 2's `turu recall branch` already surfaced the recent sessions):
42
55
  ```bash
43
56
  grep -rl "<slug>" "$JOURNAL"/"$LOG_SUBDIR"/YYYY/YYYY-MM/ 2>/dev/null | tail -3
44
57
  ```
45
58
  Read any matches to understand recent session history.
46
59
 
47
- 6. Search inbox for related items:
60
+ 7. Search inbox for related items (skip when `turu recall branch` already surfaced them):
48
61
  ```bash
49
62
  grep -i "<slug>" "$JOURNAL"/inbox.md
50
63
  ```
51
64
 
52
- 7. **Check for accumulated whisper knowledge.**
65
+ 8. **Load whisper knowledge** — only for the turu-absent branch of step 2
66
+ (when turu is available, `turu recall` already ran there; do not repeat
67
+ or hand-roll it):
53
68
 
54
- **If `turu` is available** (`turu key --json` succeeds), delegate every
55
- mechanical step to it — never hand-roll repo-key or path derivation:
56
- ```bash
57
- turu key --json # canonical repo key, branch slug, worktree slot
58
- turu recall repo # repo-scope knowledge (env facts)
59
- turu recall branch # branch-scope knowledge (notes)
60
- turu recall worktree # worktree-slot knowledge (only when step 8 uses one)
61
- ```
62
- - `turu recall` output already routes to the right store (global, repo,
63
- or repo-local `.whisper/`), so never `ls`/`find` `~/.whisper/` to guess
64
- paths — canonical keys don't match raw remote URLs.
65
- - `turu recall` exits non-zero with `nothing to recall in this scope`
66
- when a scope is empty — treat that as "no knowledge here", not a
67
- failure; move on without improvising alternate lookup paths.
68
-
69
- **Fallback (turu absent):** if `~/.whisper/` exists, load context with:
69
+ If `~/.whisper/` exists, load context with:
70
70
  ```bash
71
71
  repo_url=$(git remote get-url origin 2>/dev/null | sed 's|https://||;s|git@||;s|\.git$||')
72
72
  branch_slug=$(git rev-parse --abbrev-ref HEAD | sed 's|/|--|g')
@@ -87,7 +87,9 @@ Uses `$JOURNAL_PATH` (defaults to `~/dev/status`) for the daily log journal, and
87
87
  ```
88
88
  Surface any `in_progress` tickets prominently. The **Suggested next step** must only reference tickets NOT currently `in_progress`.
89
89
 
90
- 8. If the project/area has a worktree or repo path noted in its file, gather git context:
90
+ 9. If the project/area has a worktree or repo path noted in its file, gather git context:
91
+ - When turu is available and a worktree is actually used, also run
92
+ `turu recall worktree` for its slot knowledge.
91
93
  - `cd <worktree-path> && git branch --show-current`
92
94
  - `git log --oneline -5`
93
95
  - `git status --short`