githits 0.1.7 → 0.1.9

package/dist/index.js

@@ -1,6 +1,6 @@
 import {
   version
-} from "./shared/chunk-hg653b0a.js";
+} from "./shared/chunk-ey1zffpv.js";
 export {
   version
 };

package/dist/shared/{chunk-hg653b0a.js → chunk-ey1zffpv.js}

@@ -1,4 +1,4 @@
 // package.json
-var version = "0.1.7";
+var version = "0.1.9";
 
 export { version };

package/gemini-extension.json

@@ -0,0 +1,12 @@
+{
+  "name": "githits",
+  "version": "0.1.9",
+  "description": "Code examples from global open source for developers and AI assistants.",
+  "mcpServers": {
+    "githits": {
+      "command": "npx",
+      "args": ["-y", "githits@latest", "mcp", "start"]
+    }
+  },
+  "contextFileName": "GEMINI.md"
+}

package/package.json

@@ -1,11 +1,19 @@
 {
   "name": "githits",
   "description": "CLI companion for GitHits - code examples from global open source for developers and AI assistants",
-  "version": "0.1.7",
+  "version": "0.1.9",
   "type": "module",
   "files": [
     "dist",
-    "LICENSE"
+    "LICENSE",
+    ".plugin",
+    ".claude-plugin",
+    ".mcp.json",
+    "gemini-extension.json",
+    "GEMINI.md",
+    "plugins",
+    "skills",
+    "commands"
   ],
   "module": "./dist/index.js",
   "types": "./dist/index.d.ts",

package/plugins/claude/.claude-plugin/plugin.json

@@ -0,0 +1,12 @@
+{
+  "name": "githits",
+  "version": "0.1.9",
+  "description": "Code examples from global open source for developers and AI assistants",
+  "author": {
+    "name": "GitHits"
+  },
+  "homepage": "https://githits.com",
+  "repository": "https://github.com/githits-com/githits-cli",
+  "license": "Apache-2.0",
+  "keywords": ["githits", "code-examples", "search", "mcp", "ai"]
+}

package/plugins/claude/.mcp.json

@@ -0,0 +1,8 @@
+{
+  "mcpServers": {
+    "githits": {
+      "command": "npx",
+      "args": ["-y", "githits@latest", "mcp", "start"]
+    }
+  }
+}

package/plugins/claude/commands/help.md

@@ -0,0 +1,46 @@
+---
+description: Show available GitHits commands and usage
+disable-model-invocation: true
+---
+
+# GitHits Help
+
+Run the GitHits CLI help command in the terminal:
+
+```
+npx -y githits help
+```
+
+Then display the command output clearly to the user, followed by this plugin
+context summary:
+
+## Slash Commands
+
+- `/githits:search <query>` — Search for code examples from open source.
+- `/githits:login` — Authenticate with your GitHits account.
+- `/githits:status` — Show your current authentication status.
+- `/githits:logout` — Remove stored credentials.
+- `/githits:help` — Show this help message.
+
+## MCP Tools
+
+This plugin connects to the GitHits MCP server and exposes three tools:
+
+- **search** — Find code examples by describing what you need in natural
+  language. Requires `query` and `language` parameters.
+- **search_language** — Look up supported programming language names before
+  searching.
+- **feedback** — Rate a search result to improve future quality.
+
+## Authentication
+
+Run `npx -y githits login` to authenticate via browser, or set the
+`GITHITS_API_TOKEN` environment variable for headless environments.
+
+If users want to verify MCP tools loaded, suggest `/mcp`.
+
+If the command fails, report the error and suggest running:
+
+```
+npx -y githits login
+```

package/plugins/claude/commands/login.md

@@ -0,0 +1,36 @@
+---
+description: Log in to your GitHits account
+---
+
+# Login
+
+Authenticate the user with GitHits by running the CLI login command in the
+terminal:
+
+```
+npx -y githits login
+```
+
+This opens the user's browser for secure OAuth authentication. Tokens are stored
+locally and refreshed automatically.
+
+If the environment has no display (SSH, CI, containers), use the `--no-browser`
+flag instead:
+
+```
+npx -y githits login --no-browser
+```
+
+This prints a URL the user can open on another device.
+
+Other useful flags:
+
+- `--force` — re-authenticate even if already logged in.
+- `--port <port>` — use a specific port for the local callback server.
+
+After running the command, inform the user of the result. If login succeeds,
+confirm they are authenticated. If it fails, provide the error and suggest they
+try again.
+
+Alternative: the user can set the `GITHITS_API_TOKEN` environment variable
+instead of using browser login.

package/plugins/claude/commands/logout.md

@@ -0,0 +1,16 @@
+---
+description: Log out of your GitHits account
+---
+
+# Logout
+
+Sign the user out of GitHits by running the CLI logout command in the terminal:
+
+```
+npx -y githits logout
+```
+
+This removes the locally stored authentication tokens.
+
+Confirm to the user that they have been logged out successfully. If the logout
+fails, provide the error details.

package/plugins/claude/commands/search.md

@@ -0,0 +1,23 @@
+---
+description: Search for code examples from open source via GitHits
+---
+
+# Search
+
+Search for code examples using GitHits for the query: "$ARGUMENTS"
+
+Use the GitHits MCP `search` tool with the user's query. The tool requires two
+parameters:
+
+- **query**: The user's search query, formulated in natural language.
+- **language**: The programming language. If the language is unclear from
+  context, use the `search_language` tool first to find the correct language
+  name.
+
+Optional parameter:
+
+- **license_mode**: `"strict"` (default, excludes copyleft), `"yolo"` (all
+  licenses), or `"custom"` (user's blocklist).
+
+Present the results clearly. After the user has reviewed the result, use the
+`feedback` tool to report whether the example was helpful.

package/plugins/claude/commands/status.md

@@ -0,0 +1,22 @@
+---
+description: Show your GitHits authentication status
+---
+
+# Status
+
+Check the user's current GitHits authentication status by running the CLI
+command in the terminal:
+
+```
+npx -y githits auth status
+```
+
+This shows whether the user is authenticated, where credentials are sourced
+from, and token expiry details when available.
+
+After running the command, report the status clearly. If the user is not
+authenticated, suggest running:
+
+```
+npx -y githits login
+```

package/plugins/claude/skills/search/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: search
+description:
+  Use GitHits MCP tools to find real-world code examples when model knowledge
+  is insufficient.
+---
+
+Use GitHits when:
+
+- You are blocked, uncertain about an API, or need up-to-date OSS usage.
+- You have attempted a solution twice and it still fails - search for a working example before trying again.
+- The user asks to search for examples or explicitly mentions GitHits.
+- You are implementing non-trivial code in languages where confidence is lower.
+
+Authentication:
+
+- If any GitHits tool returns an authentication error, immediately run
+  `npx -y githits login` in the terminal. This opens the user's browser for
+  quick OAuth approval. Wait for the command to complete, then retry the
+  original tool call.
+- If the environment has no display (SSH, containers), use
+  `npx -y githits login --no-browser` instead, which prints a URL for the
+  user to open on another device.
+- Do NOT ask the user to run login manually -- handle it automatically.
+- If login fails, inform the user of the error and suggest they set the
+  `GITHITS_API_TOKEN` environment variable as an alternative.
+
+Guidelines:
+
+- Prefer existing search context if it already answers the problem.
+- Use `search_language` first when language naming is uncertain.
+- Use `search` for one focused question at a time.
+- After using results, send `feedback` with helpful/unhelpful outcome.
+
+Tool argument details and rich query guidance are provided directly in the MCP
+tool descriptions; follow those descriptions as the source of truth.

package/skills/search/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: search
+description:
+  Use GitHits MCP tools to find real-world code examples when model knowledge
+  is insufficient.
+---
+
+Use GitHits when:
+
+- You are blocked, uncertain about an API, or need up-to-date OSS usage.
+- You have attempted a solution twice and it still fails - search for a working example before trying again.
+- The user asks to search for examples or explicitly mentions GitHits.
+- You are implementing non-trivial code in languages where confidence is lower.
+
+Authentication:
+
+- If any GitHits tool returns an authentication error, immediately run
+  `npx -y githits login` in the terminal. This opens the user's browser for
+  quick OAuth approval. Wait for the command to complete, then retry the
+  original tool call.
+- If the environment has no display (SSH, containers), use
+  `npx -y githits login --no-browser` instead, which prints a URL for the
+  user to open on another device.
+- Do NOT ask the user to run login manually -- handle it automatically.
+- If login fails, inform the user of the error and suggest they set the
+  `GITHITS_API_TOKEN` environment variable as an alternative.
+
+Guidelines:
+
+- Prefer existing search context if it already answers the problem.
+- Use `search_language` first when language naming is uncertain.
+- Use `search` for one focused question at a time.
+- After using results, send `feedback` with helpful/unhelpful outcome.
+
+Tool argument details and rich query guidance are provided directly in the MCP
+tool descriptions; follow those descriptions as the source of truth.