@rhize/skill-forge 0.17.0 → 0.19.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/LICENSE +1 -0
- package/README.md +20 -3
- package/dist/cli.js +1374 -797
- package/dist/cli.js.map +1 -1
- package/dist/refine-prompt.md +10 -0
- package/package.json +1 -1
package/dist/refine-prompt.md
CHANGED
|
@@ -372,3 +372,13 @@ After applying (project-scope capture, or a user-scope promote):
|
|
|
372
372
|
Close with a short summary: which skill, what gap, which override type/action, what was written
|
|
373
373
|
and where, the refinement id, whether it joined an existing pattern (and which), and the
|
|
374
374
|
verification result. Keep it concise — the store itself is the durable record.
|
|
375
|
+
|
|
376
|
+
## Explicit project activation (0.19)
|
|
377
|
+
|
|
378
|
+
A captured patch/extend is not proof of host use. To activate, use `refine activate`
|
|
379
|
+
with the exact `--skill` capture, read-only `--base`, unique `--as` project name and
|
|
380
|
+
`--host claude|codex`. Preview with `--dry-run --json`, inspect safety and companion
|
|
381
|
+
files, then confirm. Never edit a plugin cache. Persist the returned source identity,
|
|
382
|
+
backup and rollback command. Verify the exact loaded file in a fresh host task and
|
|
383
|
+
retry the original failure before claiming success; unavailable verification stays
|
|
384
|
+
pending. `refine rollback <backup-id> --project --yes` refuses later edits.
|