Make agents use your project right

Being useful isn't enough if agents can't use it

An agent may not know your library exists, or that you've released a new version. It may reach for a familiar alternative, rebuild what you've already solved, or write code against an API you've changed.

That costs you adoption and creates broken integrations and support work. Agents need knowledge beyond their training to adopt your project and keep using it correctly.

Give agents the knowledge to use your project right

• Make your actual API the reference. Agents can look up your project's available source, docs, and package data, including releases absent from their training.
• Support the software built on your project. Agents can trace failures into your implementation and examine release changes before upgrading.
• Show how problems are solved. Cross-project example discovery helps agents find relevant implementations beyond the packages they already know.

From package choice to the next upgrade

An agent implementing a feature can use GitHits to investigate your library, read its API, and integrate the selected version. When an error appears, it can inspect your implementation. When you release a new version, it can examine what changed and adapt the integration.

Your code and documentation inform the work at each step, through the same interface the agent uses for its other open-source dependencies.

Add GitHits to your README

Find your repository in the GitHits Index: choose GitHub and enter your owner/repository. Copy the badge Markdown from its page into your README.

The badge shows index status and links to your project's page, making GitHits discoverable from your repository. Agents connected to GitHits can query your project's available code and documentation.