@codacy/verity-cli 0.28.1-experimental.9155758 → 0.28.1-experimental.af3c52d

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

@@ -20,7 +20,8 @@ You are running an on-demand Verity analysis. This is like a "second opinion"
    - **Fails / not authenticated**: don't stop. Tell the user Verity is in
      **local-only mode**, so the review will run static analysis and show findings
      but won't perform the deep (LLM) review or upload anything. To unlock the deep
-     review they can authenticate with `verity init` (or `verity auth register`).
+     review they can authenticate with `verity login` (one login covers every
+     repository they can write to).
      Continue — `verity review` degrades to a local static-only report on its own.
 
 ---

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

@@ -341,21 +341,26 @@ verity auth verify
   deep review, history, and shareable reports by running:
 
   ```bash
-  verity init          # re-runs init; offers the auth prompt again
-  # or, directly:
-  verity auth register --project "PROJECT_NAME" --remote "GIT_REMOTE_URL"
+  verity login         # one GitHub login covers every repo you can write to
+  # or: verity init    # re-runs init; offers the same auth prompt
   ```
 
-  Registration is **provider-gated** (GitHub today): the CLI runs a GitHub App
-  **device flow** ("open https://github.com/login/device and enter code
-  WXYZ-1234"), proving the user has **write access** to the repo before the
-  service issues a token. The GitHub App requests only read-only permissions
-  (Metadata + Email addresses); the resulting token is used once server-side to
-  check repo access and is never persisted.
-
-When authenticated, the project's `token` and `service_url` are stored in the
-single global credentials file `~/.verity/credentials` (keyed by git remote) —
-nothing secret is written into the repo. All subsequent `verity` upload commands work.
+  Login is **provider-gated** (GitHub today): the CLI runs a GitHub App **device
+  flow** ("open https://github.com/login/device and enter code WXYZ-1234"),
+  proving the user has **write access** before the service issues a token. The
+  GitHub App requests only read-only permissions (Metadata + Email addresses);
+  the provider token is used once server-side to sweep the repositories the user
+  can write to, and is never persisted.
+
+  **One login covers every repository** the user can write to, not just this one.
+  Re-running `verity login` is also how access to newly-granted repos is picked
+  up, and how an expired verification is restored. If login reports this
+  repository is **not covered**, the Verity GitHub App has not been granted
+  access to it — grant it, then re-run `verity login`.
+
+When authenticated, the user's `token` and `service_url` are stored in the single
+global credentials file `~/.verity/credentials` — nothing secret is written into
+the repo. All subsequent `verity` upload commands work.
 
 ---
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@codacy/verity-cli",
-  "version": "0.28.1-experimental.9155758",
+  "version": "0.28.1-experimental.af3c52d",
   "description": "CLI for Verity quality gate service",
   "homepage": "https://verity.md",
   "bugs": {