Fehm with Gemini CLI

Set up Fehm in Gemini CLI. Install the skill, choose a scope, build a local graph, and query repository context.

Give Gemini CLI a repeatable way to map a repository and retrieve source-backed context. Install the Fehm CLI first using the installation guide.

Install and register

Terminal
fehm install --platform gemini

This registers a personal skill at ~/.gemini/skills/fehm/SKILL.md. For a project-only setup, run from the repository root:

Terminal
fehm install --project --platform gemini

Project scope writes .gemini/skills/fehm/SKILL.md. The installer reports the path and preserves customized files.

Build the graph

Ask Gemini to use the Fehm skill to map the current repository. Restart or reload the assistant if it has not discovered the skill.

Terminal
fehm scan .

The graph is stored in .fehm/graph.json. Run scans from the repository being analyzed, not the skill installation folder.

Ask with context

Use Fehm to explain the authentication flow. Cite source files and distinguish explicit relationships from inferred ones.

You can also retrieve the context in a terminal:

Terminal
fehm query "authentication flow"

Keep the integration current

Install the next supplied wheel, then refresh the original scope:

Terminal
fehm install --platform gemini
fehm integrations --platform gemini

Add --project if that was your installation scope. Once the registry package is released, use uv tool upgrade fehm before re-registering.

Troubleshooting

Confirm the CLI is on the assistant terminal’s PATH and the skill is in the intended scope. Remote hosts need their own Fehm installation. If the skill does not appear, reload your assistant and check that skills are enabled.

More troubleshooting · Connect with MCP instead