githits 0.2.1 → 0.2.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/index.js CHANGED
@@ -1,6 +1,6 @@
1
1
  import {
2
2
  version
3
- } from "./shared/chunk-szjytcvw.js";
3
+ } from "./shared/chunk-js72s35a.js";
4
4
  export {
5
5
  version
6
6
  };
@@ -2,8 +2,8 @@ import {
2
2
  createContainer,
3
3
  resolveStartupCodeNavigationCapability,
4
4
  resolveStartupCodeNavigationRegistrationState
5
- } from "./chunk-ykr7x8jp.js";
6
- import"./chunk-szjytcvw.js";
5
+ } from "./chunk-a9js75mw.js";
6
+ import"./chunk-js72s35a.js";
7
7
  export {
8
8
  resolveStartupCodeNavigationRegistrationState,
9
9
  resolveStartupCodeNavigationCapability,
@@ -1,6 +1,6 @@
1
1
  import {
2
2
  version
3
- } from "./chunk-szjytcvw.js";
3
+ } from "./chunk-js72s35a.js";
4
4
 
5
5
  // src/services/auth-service.ts
6
6
  import { createServer } from "node:http";
@@ -1,6 +1,6 @@
1
1
  import { createRequire } from "node:module";
2
2
  var __require = /* @__PURE__ */ createRequire(import.meta.url);
3
3
  // package.json
4
- var version = "0.2.1";
4
+ var version = "0.2.3";
5
5
 
6
6
  export { __require, version };
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "githits",
3
- "version": "0.2.1",
3
+ "version": "0.2.3",
4
4
  "description": "Code examples from global open source for developers and AI assistants.",
5
5
  "mcpServers": {
6
6
  "githits": {
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "githits",
3
3
  "description": "CLI companion for GitHits - code examples from global open source for developers and AI assistants",
4
- "version": "0.2.1",
4
+ "version": "0.2.3",
5
5
  "type": "module",
6
6
  "files": [
7
7
  "dist",
@@ -72,6 +72,7 @@
72
72
  "@modelcontextprotocol/sdk": "^1.23.0",
73
73
  "@napi-rs/keyring": "^1.2.0",
74
74
  "commander": "^14.0.2",
75
+ "jsonc-parser": "^3.3.1",
75
76
  "open": "^11.0.0",
76
77
  "zod": "^4.1.13"
77
78
  },
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "githits",
3
- "version": "0.2.1",
3
+ "version": "0.2.3",
4
4
  "description": "Code examples from global open source for developers and AI assistants",
5
5
  "author": {
6
6
  "name": "GitHits"
@@ -6,16 +6,17 @@ description: Search for canonical code examples from open source via GitHits
6
6
 
7
7
  Search for code examples using GitHits for the query: "$ARGUMENTS"
8
8
 
9
- Use the GitHits MCP `get_example` tool with the user's query. The tool requires two
10
- parameters:
9
+ Use the GitHits MCP `get_example` tool with the user's query.
10
+
11
+ Required parameter:
11
12
 
12
13
  - **query**: The user's search query, formulated in natural language.
13
- - **language**: The programming language. If the language is unclear from
14
- context, use the `search_language` tool first to find the correct language
15
- name.
16
14
 
17
- Optional parameter:
15
+ Optional parameters:
18
16
 
17
+ - **language**: The programming language. Omit it to let GitHits infer the
18
+ language from the query. If you need to force a specific language and the
19
+ exact name is uncertain, use the `search_language` tool first.
19
20
  - **license_mode**: `"strict"` (default, excludes copyleft), `"yolo"` (all
20
21
  licenses), or `"custom"` (user's blocklist).
21
22
 
@@ -28,9 +28,9 @@ context summary:
28
28
  This plugin connects to the GitHits MCP server and always exposes three core tools:
29
29
 
30
30
  - **get_example** — Find code examples by describing what you need in natural
31
- language. Requires `query` and `language` parameters.
32
- - **search_language** — Look up supported programming language names before
33
- searching.
31
+ language. Requires `query`; `language` is optional and inferred when omitted.
32
+ - **search_language** — Look up supported programming language names when you
33
+ need to force a specific language.
34
34
  - **feedback** — Rate a search result to improve future quality.
35
35
 
36
36
  Additional indexed dependency/package tools such as `search`, `package_summary`,
@@ -8,16 +8,17 @@ Use GitHits example search for the query: "$ARGUMENTS"
8
8
 
9
9
  This slash command is the older alias for `/githits:example`.
10
10
 
11
- Use the GitHits MCP `get_example` tool with the user's query. The tool requires two
12
- parameters:
11
+ Use the GitHits MCP `get_example` tool with the user's query.
12
+
13
+ Required parameter:
13
14
 
14
15
  - **query**: The user's search query, formulated in natural language.
15
- - **language**: The programming language. If the language is unclear from
16
- context, use the `search_language` tool first to find the correct language
17
- name.
18
16
 
19
- Optional parameter:
17
+ Optional parameters:
20
18
 
19
+ - **language**: The programming language. Omit it to let GitHits infer the
20
+ language from the query. If you need to force a specific language and the
21
+ exact name is uncertain, use the `search_language` tool first.
21
22
  - **license_mode**: `"strict"` (default, excludes copyleft), `"yolo"` (all
22
23
  licenses), or `"custom"` (user's blocklist).
23
24
 
@@ -28,7 +28,8 @@ Authentication:
28
28
  Guidelines:
29
29
 
30
30
  - Prefer existing search context if it already answers the problem.
31
- - Use `search_language` first when language naming is uncertain.
31
+ - Pass `language` only when you need to force a specific language; use
32
+ `search_language` first if the exact language name is uncertain.
32
33
  - Use `get_example` for one focused example-search question at a time.
33
34
  - When the task is about indexed dependency or repository internals and the
34
35
  capability-gated tools are available, prefer unified `search` instead of
@@ -28,7 +28,8 @@ Authentication:
28
28
  Guidelines:
29
29
 
30
30
  - Prefer existing search context if it already answers the problem.
31
- - Use `search_language` first when language naming is uncertain.
31
+ - Pass `language` only when you need to force a specific language; use
32
+ `search_language` first if the exact language name is uncertain.
32
33
  - Use `get_example` for one focused example-search question at a time.
33
34
  - When the task is about indexed dependency or repository internals and the
34
35
  capability-gated tools are available, prefer unified `search` instead of