integrations

Gemini Integration

Connect Docmancer to Gemini CLI so it starts from the same local memory as every other coding agent on your machine.

Install

docmancer agent install gemini

This installs the skill to two locations:

PathPurpose
~/.gemini/skills/docmancer/SKILL.mdPrimary Gemini skill path
~/.agents/skills/docmancer/SKILL.mdShared compatibility path (if not already present)

The shared path provides compatibility with other agents that read from ~/.agents/skills/.

Project-local installation

Install the skill in the current project instead of globally:

docmancer agent install gemini --project

This creates the skill at .gemini/skills/docmancer/SKILL.md in your project directory.

Verify

docmancer status

Look for the gemini entry under agent delivery.

Verify with one prompt

Ask Gemini CLI: Before changing deployment code, recall what we decided about production hosting.

The expected behaviour is a project-scoped memory query before edits and a concise answer tied to the memory it returns. When nothing matches, Gemini should say so plainly instead of filling the gap with a guess.

Restart note

Gemini CLI may not pick up a newly installed skill immediately. If docmancer commands are not being used, restart Gemini.

Add docs and query

Make sure you have documentation indexed:

docmancer docs add https://docs.pytest.org

Then ask Gemini about the docs. The installed skill teaches Gemini to call docmancer docs query and receive a token-budgeted context pack from your local index.