@codacy/verity-cli 0.32.0-experimental.cc76941 → 0.32.0-experimental.f0746f7

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

@@ -1,10 +1,3 @@
----
-description: >-
-  Run an independent AI review of the current change on demand — a second opinion on quality,
-  security, and whether the code matches its stated intent. Use when the user asks to review,
-  check, or analyze code before committing, or to get an independent check on work you have
-  just finished.
----
 # /verity-analyze — Run Verity analysis on demand
 
 You are running an on-demand Verity analysis. This is like a "second opinion" — the user (or you) can invoke it at any point to get a quality and security review with rich context.

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

@@ -1,9 +1,3 @@
----
-description: >-
-  Send the user's feedback about Verity to the Verity team, verbatim. Use only when the user
-  explicitly asks to send feedback.
-disable-model-invocation: true
----
 # /verity-feedback — Send feedback
 
 ## General feedback

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

@@ -1,10 +1,3 @@
----
-description: >-
-  Report project quality metrics from accumulated run data, and manage the Standard's evolution
-  suggestions. Use when the user asks for quality trends or metrics, or whether the Standard
-  should change.
-disable-model-invocation: true
----
 # /verity-insights — Project quality insights and Standard evolution
 
 Surface metrics from accumulated run data and manage Standard evolution suggestions.

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

@@ -1,9 +1,3 @@
----
-description: >-
-  View and manage the durable project knowledge Verity has accumulated — decisions, patterns,
-  gotchas, and conventions extracted from past analysis runs. Use when the user asks what
-  Verity has learned, or before changing an area of the code you do not know.
----
 # /verity-learn — View and manage project knowledge
 
 Project knowledge is durable insights extracted from analysis runs — decisions, patterns, gotchas, and conventions. When the memory graph is enabled (`memory_graph_enabled`), this skill delegates to the graph. Otherwise, it uses flat lessons.

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

@@ -1,10 +1,3 @@
----
-description: >-
-  Browse, query, and extend the project knowledge graph at .verity/memory/ — typed nodes and
-  edges covering decisions, patterns, security constraints, and gotchas. Use to pull prior
-  context on files you are about to change, or when the user asks to record or inspect project
-  knowledge.
----
 # /verity-memory — Manage the project knowledge graph
 
 The memory graph is a collection of markdown nodes at `.verity/memory/` organized into 8 domains. Each node has YAML frontmatter with typed edges that form a graph. The graph is the project's accumulated knowledge — decisions, patterns, gotchas, security constraints, and more.

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

@@ -1,9 +1,3 @@
----
-description: >-
-  Capture a durable learning at the end of a task: draft a concrete, cited observation from
-  what actually happened, then confirm it with the user or record it directly. Use at natural
-  task-completion moments, or when the user asks to record a lesson.
----
 # /verity-reflect — Capture learnings after a task
 
 At a natural task-completion moment, **the agent reflects first** — draft a

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

@@ -1,10 +1,3 @@
----
-description: >-
-  Configure Verity for this project: create or update the project Standard, wire the
-  static-analysis tools, and authenticate. Use when setting Verity up for the first time, or
-  when the user asks to change quality rules, severity thresholds, or which analysis tools run.
-disable-model-invocation: true
----
 # /verity-setup — Configure Verity for this project
 
 You are finishing Verity's setup: the half that needs a model.
@@ -35,7 +28,7 @@ propose them from evidence rather than have them invented from a dependency list
 3. Write `.codacy/codacy.config.json` with curated, validated pattern ids (Step 5).
 4. Upload both, seed the knowledge base, write `VERITY.md` (Steps 7–8).
 
-**Reference files** (bundled alongside this skill, at `${CLAUDE_SKILL_DIR}`):
+**Reference files** (installed in this project at `.claude/skills/verity-setup/`):
 - `patterns-reference.yaml` — Research-backed patterns catalog (quality, security, language-specific)
 - `standard-template.yaml` — YAML skeleton for the Standard
 
@@ -155,7 +148,7 @@ user's decision to make at a terminal.
 
 ## Step 4: Synthesize the Standard
 
-Read `${CLAUDE_SKILL_DIR}/patterns-reference.yaml` and `${CLAUDE_SKILL_DIR}/standard-template.yaml`.
+Read `.claude/skills/verity-setup/patterns-reference.yaml` and `.claude/skills/verity-setup/standard-template.yaml` from the project root.
 
 Generate `.verity/standard.yaml` by filling in the template:
 
@@ -228,7 +221,7 @@ it from the installed adapter. Then **always validate** (next section).
 
    ```bash
    # balanced/thorough: critical + high vulns, secrets, malicious packages
-   node ${CLAUDE_SKILL_DIR}/validate-patterns.mjs --emit Trivy \
+   node <skill-dir>/validate-patterns.mjs --emit Trivy \
      '^Trivy_(secret|malicious_packages|vulnerability_(critical|high))$'
 
    # lightweight: drop malicious_packages if you want the minimum
@@ -413,7 +406,7 @@ alongside this skill. It checks every `patternId` against the IDs the installed
 adapters actually define, and exits non-zero on any that does not exist:
 
 ```bash
-node ${CLAUDE_SKILL_DIR}/validate-patterns.mjs
+node "$(dirname "$0")/validate-patterns.mjs"   # or: node <skill-dir>/validate-patterns.mjs
 ```
 
 Expected output:
@@ -481,7 +474,7 @@ disabled tool produces the same zero findings as clean code, so a quiet run prov
 nothing on its own:
 
 ```bash
-node ${CLAUDE_SKILL_DIR}/validate-patterns.mjs
+node <skill-dir>/validate-patterns.mjs
 ```
 
 Then confirm the volume is sane:

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

@@ -1,9 +1,3 @@
----
-description: >-
-  Show Verity quality status for this project: Standard version, last run summary, quality
-  trend, and pending items. Use when the user asks how the project is doing, what Verity found
-  recently, or whether the gate is passing.
----
 # /verity-status — Show Verity quality status
 
 You are showing the current Verity quality status for this project. This gives a quick overview of project health without running a new analysis.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@codacy/verity-cli",
-  "version": "0.32.0-experimental.cc76941",
+  "version": "0.32.0-experimental.f0746f7",
   "description": "CLI for Verity quality gate service",
   "license": "SEE LICENSE IN LICENSE",
   "homepage": "https://verity.md",