Guides
Trigger GitHits manually
Prompt your agent to use GitHits when it does not call the tools on its own.
Some agent harnesses call MCP tools aggressively. Others wait until you ask for a specific kind of research. If your agent is guessing, looping, or relying on generic knowledge, tell it directly to use GitHits.
For a broader view of when to use GitHits during planning, implementation, and debugging, see Use GitHits in agentic coding workflows.
Good for unfamiliar APIs, integration patterns, and current ecosystem conventions.
Good when a stack trace points into a dependency, docs do not explain a behavior, or the agent keeps guessing. The agent can usually infer the package version from your repo.
Good when hosted docs or repo-backed docs are needed inside the agent session.
Good for dependency triage, vulnerability checks, and upgrade context.