@open-tomato/rafa 0.20.0 → 0.21.0
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.
- package/README.md +39 -1
- package/dist/cli.js +1143 -329
- package/dist/effort/store/index.js +1 -1
- package/dist/{index-afersvp3.js → index-am92b8qp.js} +26 -5
- package/dist/{index-zhh1h3h9.js → index-kv51t295.js} +40 -4
- package/dist/{index-02fx0mzf.js → index-pzpk59ma.js} +3255 -2524
- package/dist/index.js +2 -2
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -171,6 +171,44 @@ the next one, so you rarely have to remember it.
|
|
|
171
171
|
|
|
172
172
|
Then step 2 again, or `rafa plan create --next`.
|
|
173
173
|
|
|
174
|
+
### Tracking effort and learning from skills
|
|
175
|
+
|
|
176
|
+
Each run records what it cost in time, tokens and work, and which skills
|
|
177
|
+
were offered, invoked and worked. Two commands read that record:
|
|
178
|
+
|
|
179
|
+
```bash
|
|
180
|
+
rafa effort collect # gather and store session logs
|
|
181
|
+
rafa effort report # per-plan summary: sessions, tasks, costs
|
|
182
|
+
```
|
|
183
|
+
|
|
184
|
+
`rafa effort report` shows the per-plan tables (sessions by status and
|
|
185
|
+
outcome), the task report tallies, and any runs whose preflight halted. To
|
|
186
|
+
see which skills earned their place and which are ignored:
|
|
187
|
+
|
|
188
|
+
```bash
|
|
189
|
+
rafa effort report --skills
|
|
190
|
+
rafa effort report --skills --plan=rafa-24-know-which-skills-earn
|
|
191
|
+
```
|
|
192
|
+
|
|
193
|
+
With `--skills`, the report shows per plan and per resolver (the method
|
|
194
|
+
that picked which skills to offer: `planner` by task declaration, `tag`
|
|
195
|
+
by ranking, or `none`):
|
|
196
|
+
|
|
197
|
+
- Each **skill**: offered count, invoked count, reported in the outcome,
|
|
198
|
+
recurrence count, and its **signal**: `earning` (worked with no failure
|
|
199
|
+
recurrence), `recurring` (invoked but a failure recurred), `unmeasured`
|
|
200
|
+
(invoked with no failure strings declared), or `ignored` (offered but
|
|
201
|
+
never invoked).
|
|
202
|
+
- Each **lesson**: injected count, recurrence count, and whether it
|
|
203
|
+
recurred.
|
|
204
|
+
- **M1** and **M2**: how many task lines used skills you offered, and how
|
|
205
|
+
many of the skills you offered were actually invoked.
|
|
206
|
+
- **Plan CI**: the settled result of the pull request's checks when it landed.
|
|
207
|
+
|
|
208
|
+
The report opens with a fixed line explaining that it shows co-occurrence,
|
|
209
|
+
not causation: a skill can be invoked and its failure recur for reasons the
|
|
210
|
+
skill does not cover.
|
|
211
|
+
|
|
174
212
|
### Which agents and skills are involved
|
|
175
213
|
|
|
176
214
|
A task line may end with a declaration, for example
|
|
@@ -429,7 +467,7 @@ and a line here is ticked by the change that finishes the feature.
|
|
|
429
467
|
changed since you last looked
|
|
430
468
|
- ✅ The right skills reach the right task, chosen when the plan is
|
|
431
469
|
written
|
|
432
|
-
-
|
|
470
|
+
- ✅ Know which skills earn their place and which are ignored
|
|
433
471
|
- ✅ rafa learns from its own runs: what one task works out is handed
|
|
434
472
|
to the tasks that need it later
|
|
435
473
|
- ⬜ Skills and lessons shared across projects and machines
|