BLOG

Codebase intelligence, explained

Guides on auto-generated documentation, MCP tools for AI agents, git intelligence, and how repowise compares to other tools.

All posts

use-cases12 min read

How the repowise PR Bot Comments Only When It Matters

pr bot silent default is the only sane default for review automation. A GitHub PR bot should stay out of the way on green changes, then speak only when it…

2026-05-20Read →
Use git history to catch stale ADRs before they mislead agents
guides10 min read

Use git history to catch stale ADRs before they mislead agents

Use git history to flag stale decisions in an architecture decision records workflow. Catch drift early with a 500-commit view before agents follow old code.

2026-05-20Read →
AI Code Review Tools Fail When They Ignore Ownership
industry11 min read

AI Code Review Tools Fail When They Ignore Ownership

AI code review tools catch lint, but miss ownership. See how local history and nearby changes cut bad reviews and surface the right reviewer.

2026-05-20Read →
Codebase intelligence is becoming the missing layer for agents
industry11 min read

Codebase intelligence is becoming the missing layer for agents

Why the codebase intelligence category is replacing raw file access: git history, ownership, and memory cut bad changes and speed agent work.

2026-05-20Read →
What Model Context Protocol actually sends to Claude Code
mcp9 min read

What Model Context Protocol actually sends to Claude Code

See how model context protocol sends structured repo data to Claude Code, with a wire-level example and 7 tools to inspect.

2026-05-20Read →
Audit a Flask monolith before acquisition with graph, history, wiki, ADRs
use-cases12 min read

Audit a Flask monolith before acquisition with graph, history, wiki, ADRs

Run a pre-acquisition code audit on a Flask monolith with graph, git history, wiki freshness, and ADRs. Find surprises before week two.

2026-05-19Read →
Codebase RAG Breaks on Git History, Not Embeddings
industry10 min read

Codebase RAG Breaks on Git History, Not Embeddings

Why the codebase rag landscape fails after the first lookup: 4 indexing layers, 7 agent tools, and a cleaner path to ownership and change context.

2026-05-19Read →
Why vector-only retrieval misses co-change clusters in monorepos
engineering9 min read

Why vector-only retrieval misses co-change clusters in monorepos

Co-change analysis git shows which files move together, who owns them, and what breaks next. See why vector-only retrieval misses refactor signals.

2026-05-19Read →
Audit a legacy monolith before acquisition with graph, history, wiki, ADRs
use-cases10 min read

Audit a legacy monolith before acquisition with graph, history, wiki, ADRs

Audit legacy code with graph, history, wiki, and ADRs to answer ownership, risk, and rewrite questions before a deal. See 4 layers in one review.

2026-05-17Read →
Our git co-change model failed on a monorepo refactor
engineering10 min read

Our git co-change model failed on a monorepo refactor

Why co-change analysis git overfit a monorepo refactor, and the guardrails we added after 500 commits of history pointed at the wrong coupling.

2026-05-17Read →
Generate a CLAUDE.md from your repo’s ADRs and wiki
guides10 min read

Generate a CLAUDE.md from your repo’s ADRs and wiki

Generate claude.md from ADRs and wiki into a day-one agent brief: 1 file, clear rules, and links to the decisions that matter most.

2026-05-17Read →
Developer productivity metrics that survive AI coding agents
industry11 min read

Developer productivity metrics that survive AI coding agents

Developer productivity metrics should track reruns, tool calls, context churn, and time-to-first-correct-edit. Use 4 signals to replace vanity counts.

2026-05-17Read →