Githits MCP

GitHits MCP

This skill contains the stable routing guide. Do not call quick_start when this skill is loaded; this rule applies to every GitHits tool. Follow the route below, then discover the selected tool and read its argument description.

Quick-start guide

GitHits routing guide

Choose a route, discover that tool, and read its schema for syntax and defaults.

For comparisons, combine relevant package/source evidence with examples as needed.

Public OSS only; never send local/private/proprietary source. Package/repository targets use registry:name@version and github:owner/repo@ref. Omit the suffix for the latest package version or repository default branch. Package targets scope to the package subpath, including in monorepos, except for raw code_diff comparisons, which are repository-wide. Swift uses swift:github.com/<owner>/<repo>, Zig zig:gh/<owner>/<repo>. Use public repository targets for full repositories or sibling packages: github:, codeberg:, gitlab:, or a supported full URL. Never infer a provider. A ref may be a branch, tag, or commit and contain later @; # is for semantic fragments, not revisions.

resolve_target identifies canonical candidates for an OSS dependency name before evidence lookup; skip known canonical targets. Follow its continuation: only an unambiguous EXACT/HIGH best with CLEAR or NOT_APPLICABLE malicious-content status allows direct reuse. Other or missing statuses are non-actionable; CLEAR is not a vulnerability-free claim. For MEDIUM/LOW or ambiguity, narrow or explicitly choose an actionable candidate; never auto-select. A selected site: is docs-only: use list to browse or search with source:"docs".

For code_diff, pass an unversioned target and separate from/to versions or refs. Start with default name-status; use stat for magnitude or a scoped patch for content. Keep text unless required fields or the full returned patch are needed. Package diffs include sibling paths; a bounded result with no package paths does not prove the package unchanged. Treat truncation, coverage, and safety warnings as evidence limits. Raw diffs do not prove compatibility; use pkg_upgrade_review for upgrade assessment.

For grep, copy a file/page header's read locator and use its matched line numbers when more context is needed. Counts cover one page; follow continuation only as needed.

list is for a known target when you need its structure or an exact path; use search for content by topic. A package target covers its own source tree, while a repository target covers the whole snapshot; both include source and documentation. Hosted docs use a separate explicit site: inventory that list does not discover. For hosted package docs, search the package with source:"docs", then pass the explicit site: target from a [docs page] search header to list. Use snippets when sufficient; otherwise pass the returned HTTP(S) page target unchanged to read. A site: read requires a separate exact page path. For an exact section or bounds, request search JSON and replay its followUp unchanged, including supplied selector and bounds. For list text, pair a listed path with the shared read target in its header when present; a full URL row is its own read target. A site row without a trailing / is a page path even if its source URL ended in /; / itself is the site's landing page. Use JSON for exact entry kinds and per-entry read actions. Keep emitted site: read paths paired with their returned target. For list, the required target sets the site scope; selectors with or without one leading / stay within it. Hosted/crawled HTTP(S) docs locators address mutable current content. A direct HTTP(S) docs fragment read without explicit bounds returns its heading and full subtree through the next equal-or-higher heading. Repository docs are snapshot-addressed and keep returned ranges. When composing a direct read, add bounds only to intentionally select a current page range. For source, locate paths or matches, then read focused lines; never probe directories with read. Prefer source, symbols, tests, and call sites for behavioral claims. When the exact indexed code symbol or docs heading ID is known, pass it as selector to read; an optional exact path narrows code symbol lookup. Use compact package and repository target#symbol for code symbol reads; keep the fragment in target unchanged and use an exact path to narrow it. Pass HTTP(S) fragments and emitted repository docs page IDs unchanged. The unified read result determines whether the target resolved to code or docs.