@codacy/verity-cli 0.35.4 → 0.36.0

package/data/skills/verity-memory/SKILL.md

@@ -79,22 +79,70 @@ Valid kinds: `decision`, `quality`, `security`, `intent`, `gotcha`, `pattern`, `
 
 Or create the markdown file directly at `.verity/memory/<domain>/<slug>.md` with proper frontmatter (see `.verity/memory/SCHEMA.md` for the template).
 
+### Ask the graph a question
+
+```bash
+verity memory ask --json - <<'VERITY_EOF_<random>'
+why do we check the Gateway at the API level and not just TCP?
+VERITY_EOF_<random>
+```
+
+The command prints the matching nodes, best first, with their ids and paths.
+It also quotes the sentences that answer the question, each with the id of its
+node. It runs on the local files: nothing is sent, and no model writes the
+answer. Read the nodes before you rely on a quote. `--full` prints whole bodies,
+`--limit <n>` sets how many nodes come back, and `--all` includes archived nodes.
+`verity memory recall` is the same command.
+
 ### Edit a node
 
-Edit the markdown file directly at `.verity/memory/<domain>/<slug>.md`. Changes sync to the cloud on the next analysis run. User edits are always preserved (repo wins for `source: user`).
+```bash
+# Change the files the node is about. Each glob must match a file in the repository.
+verity memory edit <node-id> --file-globs scripts/verity.sh 'config/*.yaml'
+
+# Replace the body
+verity memory edit <node-id> --body - <<'VERITY_EOF_<random>'
+<the new body>
+VERITY_EOF_<random>
+
+# Or edit .verity/memory/<domain>/<slug>.md by hand (the title too), then upload it as it is
+verity memory edit <node-id>
+```
+
+The command uploads the node at once and reads it back from the service. It
+fails if the service did not take the change. `--status active|archived|superseded`
+changes only the status. If a teammate changed the node on the service since
+your last pull, the command refuses and changes nothing: run `verity memory pull`
+and edit again, or pass `--force` to overwrite their version. The source, author
+and confidence of a node stay as the service recorded them.
 
-### Archive a node
+### Delete a node
 
 ```bash
-curl -s -X PATCH -H "Authorization: Bearer $VERITY_TOKEN" \
-  -H "Content-Type: application/json" \
-  "$(verity config service-url)/compound/memory/nodes/<node_id>" \
-  -d '{"status": "archived"}'
+verity memory delete <node-id> --reason - <<'VERITY_EOF_<random>'
+<why the node is wrong or no longer applies>
+VERITY_EOF_<random>
 ```
 
-### Search nodes
+The node is archived on the service for the whole team, and its file is removed
+here. The text and the reason are kept on this machine in `.verity/.memory-trash/`.
+`verity memory restore <node-id>` undoes it.
+
+### Consolidate the graph
+
+```bash
+verity memory dream            # print the plan; changes nothing
+verity memory dream --apply    # make the changes, and save a report in .verity/dreams/
+verity memory dream --revert <dream-id>
+verity memory dream --list
+```
 
-Use full-text search via the list endpoint, or `grep -r "keyword" .verity/memory/` locally.
+`dream` merges near-duplicate nodes of one kind into the strongest one, and the
+strongest one takes over their file_globs. It also retires the nodes that the
+graph marks as superseded, and it prunes empty placeholders. It never changes a
+node with `source: user`. It lists for a person the pairs that only may be the
+same, and the contradictions that nothing in the graph settles. Show the plan
+to the user before you run `--apply`.
 
 ### Run lint
 

package/data/skills/verity-reflect/SKILL.md

@@ -47,6 +47,15 @@ VERITY_EOF_<random>
 That is the whole step. It never blocks, never prompts, and works the same in a
 TTY, a hook, CI, or a cron run.
 
+Write the title as the first line of the draft: the node is titled by its first
+line, or by the first sentence of it, up to 120 characters. The command prints
+the title it stored. If it is wrong, or the reflection is, correct it with
+`verity memory edit <node-id>` or remove it with `verity memory delete <node-id>`.
+
+Paths count when they are written from the repository root, as a file
+(`scripts/verity.sh`), a glob with a folder (`config/*.yaml`) or a folder with a
+trailing slash (`src/payments/`).
+
 The text goes through the quoted heredoc, never inside `"…"` on the command
 line: there, a `"`, a backtick or `$(…)` in the words would run in the shell.
 The quotes around the first `VERITY_EOF_<random>` are what stop the shell

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@codacy/verity-cli",
-  "version": "0.35.4",
+  "version": "0.36.0",
   "description": "CLI for Verity quality gate service",
   "license": "SEE LICENSE IN LICENSE",
   "homepage": "https://verity.md",
@@ -42,7 +42,7 @@
     "web-tree-sitter": "0.27.0"
   },
   "dependencies": {
-    "@codacy/analysis-cli": "0.25.0",
+    "@codacy/analysis-cli": "0.29.0",
     "commander": "^12",
     "yaml": "^2"
   }