incitaciones 0.10.2 → 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 +35 -13
  2. package/content/manifest.json +1 -1
  3. package/package.json +1 -1
  4. package/pi-package/skills/renew/SKILL.md +35 -13
  5. package/pi-package/skills/session/references/renew/SKILL.md +35 -13
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,34 +45,41 @@ 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 `~/.whisper/` for accumulated knowledge.**
53
- If `~/.whisper/` exists, load context:
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):
68
+
69
+ If `~/.whisper/` exists, load context with:
54
70
  ```bash
55
71
  repo_url=$(git remote get-url origin 2>/dev/null | sed 's|https://||;s|git@||;s|\.git$||')
56
72
  branch_slug=$(git rev-parse --abbrev-ref HEAD | sed 's|/|--|g')
57
73
  whisper_dir=~/.whisper/repos/"${repo_url}"/branches/"${branch_slug}"
58
74
  ```
59
- - Read `context.md` if it exists (extract beads-epic, status)
60
- - Read `plan.md` if it has real content
61
75
  - Read `notes.md` if it has real content
62
76
  - Read `env.md` at repo level for infra facts
77
+ - If the repo has a committed repo-local `.whisper/` directory, prefer
78
+ that over the global path. Its layout mirrors the global one relative
79
+ to the repo root:
80
+ `.whisper/repos/<org-path>/<repo>/branches/<branch-slug>/notes.md`
81
+ (e.g. `.whisper/repos/ak/PhormaSci/talleres/branches/main/notes.md`).
82
+
63
83
  - If beads is available, fetch open issues:
64
84
  ```bash
65
85
  bd list --label branch:<branch> 2>/dev/null
@@ -67,7 +87,9 @@ Uses `$JOURNAL_PATH` (defaults to `~/dev/status`) for the daily log journal, and
67
87
  ```
68
88
  Surface any `in_progress` tickets prominently. The **Suggested next step** must only reference tickets NOT currently `in_progress`.
69
89
 
70
- 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.
71
93
  - `cd <worktree-path> && git branch --show-current`
72
94
  - `git log --oneline -5`
73
95
  - `git status --short`
@@ -93,9 +115,9 @@ Uses `$JOURNAL_PATH` (defaults to `~/dev/status`) for the daily log journal, and
93
115
  **Related inbox items** *(if any)*
94
116
  - items that mention this project
95
117
 
96
- **Whisper context** *(if ~/.whisper/ exists)*
97
- - Plan: summary of current plan
98
- - Notes: key findings
118
+ **Whisper context** *(if turu recall or the fallback found content)*
119
+ - Env: repo-scope infra facts (`turu recall repo` / `env.md`)
120
+ - Notes: branch-scope findings (`turu recall branch` / `notes.md`)
99
121
  - Beads issues: <n> open, <n> in_progress
100
122
 
101
123
  **⚠ Active in flight** *(omit if none)*
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.2",
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,34 +59,41 @@ 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 `~/.whisper/` for accumulated knowledge.**
67
- If `~/.whisper/` exists, load context:
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):
82
+
83
+ If `~/.whisper/` exists, load context with:
68
84
  ```bash
69
85
  repo_url=$(git remote get-url origin 2>/dev/null | sed 's|https://||;s|git@||;s|\.git$||')
70
86
  branch_slug=$(git rev-parse --abbrev-ref HEAD | sed 's|/|--|g')
71
87
  whisper_dir=~/.whisper/repos/"${repo_url}"/branches/"${branch_slug}"
72
88
  ```
73
- - Read `context.md` if it exists (extract beads-epic, status)
74
- - Read `plan.md` if it has real content
75
89
  - Read `notes.md` if it has real content
76
90
  - Read `env.md` at repo level for infra facts
91
+ - If the repo has a committed repo-local `.whisper/` directory, prefer
92
+ that over the global path. Its layout mirrors the global one relative
93
+ to the repo root:
94
+ `.whisper/repos/<org-path>/<repo>/branches/<branch-slug>/notes.md`
95
+ (e.g. `.whisper/repos/ak/PhormaSci/talleres/branches/main/notes.md`).
96
+
77
97
  - If beads is available, fetch open issues:
78
98
  ```bash
79
99
  bd list --label branch:<branch> 2>/dev/null
@@ -81,7 +101,9 @@ Uses `$JOURNAL_PATH` (defaults to `~/dev/status`) for the daily log journal, and
81
101
  ```
82
102
  Surface any `in_progress` tickets prominently. The **Suggested next step** must only reference tickets NOT currently `in_progress`.
83
103
 
84
- 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.
85
107
  - `cd <worktree-path> && git branch --show-current`
86
108
  - `git log --oneline -5`
87
109
  - `git status --short`
@@ -107,9 +129,9 @@ Uses `$JOURNAL_PATH` (defaults to `~/dev/status`) for the daily log journal, and
107
129
  **Related inbox items** *(if any)*
108
130
  - items that mention this project
109
131
 
110
- **Whisper context** *(if ~/.whisper/ exists)*
111
- - Plan: summary of current plan
112
- - Notes: key findings
132
+ **Whisper context** *(if turu recall or the fallback found content)*
133
+ - Env: repo-scope infra facts (`turu recall repo` / `env.md`)
134
+ - Notes: branch-scope findings (`turu recall branch` / `notes.md`)
113
135
  - Beads issues: <n> open, <n> in_progress
114
136
 
115
137
  **⚠ Active in flight** *(omit if none)*
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,34 +45,41 @@ 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 `~/.whisper/` for accumulated knowledge.**
53
- If `~/.whisper/` exists, load context:
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):
68
+
69
+ If `~/.whisper/` exists, load context with:
54
70
  ```bash
55
71
  repo_url=$(git remote get-url origin 2>/dev/null | sed 's|https://||;s|git@||;s|\.git$||')
56
72
  branch_slug=$(git rev-parse --abbrev-ref HEAD | sed 's|/|--|g')
57
73
  whisper_dir=~/.whisper/repos/"${repo_url}"/branches/"${branch_slug}"
58
74
  ```
59
- - Read `context.md` if it exists (extract beads-epic, status)
60
- - Read `plan.md` if it has real content
61
75
  - Read `notes.md` if it has real content
62
76
  - Read `env.md` at repo level for infra facts
77
+ - If the repo has a committed repo-local `.whisper/` directory, prefer
78
+ that over the global path. Its layout mirrors the global one relative
79
+ to the repo root:
80
+ `.whisper/repos/<org-path>/<repo>/branches/<branch-slug>/notes.md`
81
+ (e.g. `.whisper/repos/ak/PhormaSci/talleres/branches/main/notes.md`).
82
+
63
83
  - If beads is available, fetch open issues:
64
84
  ```bash
65
85
  bd list --label branch:<branch> 2>/dev/null
@@ -67,7 +87,9 @@ Uses `$JOURNAL_PATH` (defaults to `~/dev/status`) for the daily log journal, and
67
87
  ```
68
88
  Surface any `in_progress` tickets prominently. The **Suggested next step** must only reference tickets NOT currently `in_progress`.
69
89
 
70
- 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.
71
93
  - `cd <worktree-path> && git branch --show-current`
72
94
  - `git log --oneline -5`
73
95
  - `git status --short`
@@ -93,9 +115,9 @@ Uses `$JOURNAL_PATH` (defaults to `~/dev/status`) for the daily log journal, and
93
115
  **Related inbox items** *(if any)*
94
116
  - items that mention this project
95
117
 
96
- **Whisper context** *(if ~/.whisper/ exists)*
97
- - Plan: summary of current plan
98
- - Notes: key findings
118
+ **Whisper context** *(if turu recall or the fallback found content)*
119
+ - Env: repo-scope infra facts (`turu recall repo` / `env.md`)
120
+ - Notes: branch-scope findings (`turu recall branch` / `notes.md`)
99
121
  - Beads issues: <n> open, <n> in_progress
100
122
 
101
123
  **⚠ Active in flight** *(omit if none)*