Menu
Use GitHits MCP tools to find real-world code examples when model knowledge is insufficient.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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.
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.
Set up GitHits from Claude Code: detect supported tools, install GitHits MCP, start sign-in/signup, verify auth, and recover from setup issues.
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.
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.
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.
| name | search |
| description | Use GitHits MCP tools to find real-world code examples when model knowledge is insufficient. |
| metadata | {"internal":true} |
Use GitHits when:
Authentication:
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.npx -y githits login --no-browser instead, which prints a URL for the
user to open on another device.GITHITS_API_TOKEN environment variable as an alternative.Guidelines:
language only when you need to force a specific language; use
search_language first if the exact language name is uncertain.get_example for one focused example-search question at a time.search instead of
get_example.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.