Product

Understand the code.
Check the evidence.

Connected workflows for developers and coding assistants, grounded in your repository.

Understand the codebase

Explore files, symbols, imports and call relationships with clickable source evidence.

Terminal
fehm search "authentication"

TypeScript and JavaScript use compiler analysis; other supported languages use shallower heuristics.

Give assistants focused context

Select relevant source and optional workflow skills under a shared context budget.

Terminal
fehm agent-context "change authentication" --skill-budget 2500

Ordinary retrieval uses no LLM. Token budgets are estimates, not exact provider counts.

Inspect architecture and drift

Explore architecture views and compare dependencies with explicit rules and detected conventions.

Terminal
fehm drift

An inferred convention is not an approved project constraint. Missing evidence does not establish compliance.

Verify changes with evidence

Inspect working-tree impact, discover checks and record approved execution in the guardrail ledger.

Terminal
fehm guardrails analyze

The richer revision-aware Change Impact Engine remains a plan. Project execution requires approval.

Review health and readiness

Inspect tests, supplied coverage, dependencies, implementation integrity and static HTML delivery signals.

Terminal
fehm health

Readiness identifies risks and missing evidence; it does not infer authorship or certify production safety.

Inspect prompts and contracts

Inventory prompts, examine evidence and compare candidates using supplied cases and recorded outputs.

Terminal
fehm prompts

Recorded outputs are not proof of a new live model run. Applying changes is a separate approved action.

Explore history and concepts

Search Git changes and inspect the evidence behind engineering concepts used in a repository.

Terminal
fehm git-memory "authentication"

Concept catalog commands require Node 22.13+. Historical analysis does not execute historical tests.

Investigate failures

Connect error output and source locations to tentative hypotheses and targeted diagnostic actions.

Terminal
fehm debug --input failure.txt --save

Static relationships do not prove root cause. Reproduction and observed checks remain necessary.

Review security evidence

Inspect static data-flow traces, trust-boundary signals and configuration concerns with source references.

Terminal
fehm security

Recognized patterns support review; unresolved flows and missing findings are not safety guarantees.

Choose engineering workflows

Route and install selected catalog skills, including detailed Superpowers planning, TDD and debugging.

Terminal
fehm skills list --source superpowers

Skills are optional instructions. They neither grant execution permission nor prove agent compliance.

SCAN · QUERY · REVIEW

Start with your repository.

Start with Fehm ↗