Skip to main content
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.

Prompt patterns

Use these prompts inside your coding agent.

Debug a dependency issue

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.

Read package documentation

Good when hosted docs or repo-backed docs are needed inside the agent session.

Review a package or upgrade

Good for dependency triage, vulnerability checks, and upgrade context.

Find a real implementation pattern

Good for unfamiliar APIs, integration patterns, and current ecosystem conventions when you do not need a version-specific source inspection.

Agent instruction snippet

Add this to your project instructions if you want stronger default behavior: