githits 0.15.1 → 0.16.0

package/server.json

@@ -16,7 +16,7 @@
     "source": "github",
     "id": "1165453165"
   },
-  "version": "0.15.1",
+  "version": "0.16.0",
   "remotes": [
     {
       "type": "streamable-http",
@@ -28,7 +28,7 @@
       "registryType": "npm",
       "registryBaseUrl": "https://registry.npmjs.org",
       "identifier": "githits",
-      "version": "0.15.1",
+      "version": "0.16.0",
       "runtimeHint": "npx",
       "transport": {
         "type": "stdio"

package/skills/githits-code/SKILL.md

@@ -68,7 +68,6 @@ githits docs read <docsReadTarget> --lines 20-120
 - If grep returns no matches, do not repeat it unchanged. Follow the returned guidance by changing the pattern, broadening the file scope, or switching to `githits search` for conceptual discovery.
 - For a missing or ambiguous standalone site, use the returned `suggestedSiteTargets` in order. Do not rewrite the original target or retry automatically; when `suggestedSiteTargetsTruncated` is true, state that additional candidates were omitted.
 - If a code-navigation command returns `INDEXING`, use the elapsed/expected duration in the message to decide whether to retry with `--wait`; prefer any displayed indexed refs/versions when you need an immediate follow-up.
-- After using GitHits results, send feedback when practical. Use `githits feedback <solution_id> --accept|--reject` for `githits example` results, or omit `<solution_id>` for generic session feedback such as `githits feedback --reject --tool search -m "missing kotlin support"`.
 
 ## External Content Posture
 

package/skills/githits-mcp/SKILL.md

@@ -17,7 +17,7 @@ recovery.
 
 GitHits provides verified open-source examples plus indexed package/repository evidence.
 
-Routing: use `get_example` for canonical cross-project examples; use `search` / `code_*` / `docs_*` / `pkg_*` for a known dependency, repository, stack trace, package adoption question, or upgrade review; use both for comparative OSS questions or when package-scoped evidence needs broader examples. Use `search_language` only to disambiguate a `get_example` language. Use `feedback` after helpful or flawed results.
+Routing: use `get_example` for canonical cross-project examples; use `search` / `code_*` / `docs_*` / `pkg_*` for a known dependency, repository, stack trace, package adoption question, or upgrade review; use both for comparative OSS questions or when package-scoped evidence needs broader examples. Use `search_language` only to disambiguate a `get_example` language.
 
 Output format: use default `text` for reading and tool follow-ups. Pass returned paths, IDs, and line ranges directly to the next tool. Use `json` only to parse responses in code or obtain required fields absent from text.
 

package/skills/githits-onboarding/SKILL.md

@@ -84,7 +84,6 @@ Follow the CLI JSON `instructions` remediation for these states rather than repl
 Tell the user:
 
 - GitHits queries and public package, repository, and documentation targets are sent to GitHits services for processing.
-- Feedback submission is an outbound write that sends feedback data to GitHits services.
 - Installing GitHits does not itself upload the local workspace.
 - After installation, open a new coding-agent session so it loads MCP configuration and any supporting instructions. The terminal and machine do not need to be restarted.
 
@@ -166,21 +165,9 @@ With `--no-browser`, surface the printed sign-in URL clearly so the user can ope
 
 7. Verify setup after login and installation.
 
-Project-level verification:
+Follow the CLI-emitted verification instruction for the selected setup scope, preserving `--project` and `--no-guidance` when applicable. Confirm selected tools are `already_configured` for that scope. For local CLI/stdio integrations, confirm local authentication is active using the auth-status command above. Skip local CLI authentication checks for Cursor-only setup; use the Cursor verification below. For mixed setups, verify each authentication path separately.
 
-```bash
-npx -y githits@latest auth status
-npx -y githits@latest init --project --detect-agents --json
-```
-
-User-level verification:
-
-```bash
-npx -y githits@latest auth status
-npx -y githits@latest init --detect-agents --json
-```
-
-Confirm auth is active and selected tools are `already_configured` for the selected scope. If MCP configuration or supporting guidance changed, tell the user to open a new coding-agent session in the project or user environment so the tool reloads its MCP configuration and any supporting instructions. The terminal and machine do not need to be restarted.
+If MCP configuration or supporting guidance changed, tell the user to open a new coding-agent session in the project or user environment so the tool reloads its MCP configuration and any supporting instructions. The terminal and machine do not need to be restarted.
 
 For Cursor, `already_configured` verifies only that the remote URL is present. It does not verify Cursor-managed OAuth or tool discovery. Do not report Cursor as ready based on `githits auth status` or init detection alone.
 

package/skills/githits-onboarding/references/troubleshooting.md

@@ -8,7 +8,7 @@ If you cannot run shell commands, explain that you cannot complete setup directl
 
 ## npx Unavailable
 
-`npx -y githits@latest` requires Node/npm tooling. If `npx` is unavailable, try an already installed `githits` binary. Otherwise explain that Node/npm or the GitHits CLI is required before agent-driven setup can continue.
+`npx -y githits@latest` requires Node/npm tooling. If `npx` is unavailable, explain that Node/npm is required before normal onboarding can continue. Do not fall back to a globally installed CLI. Use a local or pinned command only when the user explicitly requested that testing mode, preserving their command and environment.
 
 ## No Supported Tools Detected
 
@@ -48,11 +48,8 @@ For `init --install-agents <ids> --json`, inspect `outcomes`. Report each failed
 
 ## Verification Fails
 
-After setup, run:
+Follow the CLI-emitted verification instruction for the selected setup scope. Preserve `--project` for project setup and `--no-guidance` when guidance was declined; do not substitute a user-level detection command. Report the specific mismatch if selected tools are not `already_configured`.
 
-```bash
-npx -y githits@latest auth status
-npx -y githits@latest init --detect-agents --json
-```
+For local CLI/stdio integrations, check `npx -y githits@latest auth status` (or the user-requested local/pinned command). For Cursor, follow the main skill's Cursor verification flow: local CLI authentication and `already_configured` do not establish Cursor readiness. Skip local CLI authentication for Cursor-only setup; verify Cursor-managed OAuth and tool discovery in a new Cursor Agent chat, using `cursor-agent` when available. For mixed setups, verify each authentication path separately.
 
-If auth is active but selected tools are not `already_configured`, report the specific mismatch and failed tool state. If tools are configured, tell the user to open a new agent session so MCP config changes are loaded.
+After MCP configuration or supporting guidance changes, tell the user to open a new coding-agent session. The terminal and machine do not need to be restarted.