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.
Pass language only when you need to force a specific language; use search_language first if the exact language name is uncertain.
Use get_example for one focused example-search question at a time.
When the task is about indexed dependency or repository internals, prefer unified search instead of get_example.
Prefer the default compact text output. Request JSON only when exact structured fields are necessary.
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.

Más de este repositorio

mismo repositorio

githits-mcp

githits-com/githits-cli

Use GitHits MCP as an OSS context layer when a task involves open-source packages, frameworks, SDKs, libraries, developer tools, package docs, repository source, examples, planning, research, vulnerabilities, changelogs, dependency graphs, or upgrade-review evidence. Prefer it before relying on model memory or generic web search for public OSS context.

2026-07-1771

githits-release

githits-com/githits-cli

Use when preparing, reviewing, or executing a GitHits CLI release. Covers release-version consistency, plugin manifests, user-visible changelog notes, MCP instruction quality, MCP registry publishing/versioning, and the special lifecycle for published Agent Skills.

2026-07-0671

onboarding

githits-com/githits-cli

Set up GitHits from Claude Code: detect supported tools, install GitHits MCP, start sign-in/signup, verify auth, and recover from setup issues.

2026-07-0671

githits-onboarding

githits-com/githits-cli

Set up GitHits from an agent session: detect supported coding tools, install GitHits MCP configuration, start account sign-in/signup, verify auth, and recover from setup issues. Use when the user asks to install, connect, set up, sign up for, or start using GitHits.

2026-07-0671

githits-code

githits-com/githits-cli

Use GitHits CLI for canonical open-source examples, indexed source, docs, grep, file listing, and code navigation. Activate when verifying library behavior from source or examples. For metadata, vulnerabilities, dependency graphs, or changelogs, use githits-package instead.

2026-06-2671

githits-package

githits-com/githits-cli

Use GitHits CLI package-intelligence commands for package/dependency triage: overview, latest version, license, repository health, vulnerabilities, advisory history, dependency graphs, transitive provenance, changelogs, release notes, and upgrade reviews. Activate for packages, dependencies, versions, upgrades, CVEs, dependency footprints, or release changes.

2026-06-2371

name	search
description	Use GitHits MCP tools to find real-world code examples when model knowledge is insufficient.
metadata	{"internal":true}

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.
Pass language only when you need to force a specific language; use search_language first if the exact language name is uncertain.
Use get_example for one focused example-search question at a time.
When the task is about indexed dependency or repository internals, prefer unified search instead of get_example.
Prefer the default compact text output. Request JSON only when exact structured fields are necessary.
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.