Guides
Practical guides for codebase documentation, onboarding, and code quality
CLAUDE.md & AGENTS.md: The Complete Guide
What CLAUDE.md and AGENTS.md are, what to put in them, best practices, and how to keep them fresh automatically. Learn to give coding agents real repo context.
Code Health: The Complete Guide (2026)
Code health is a defect-validated measure of how risky code is to change, scored from 49 deterministic markers across three pillars. Reproduce it on your repo.
Codebase Documentation That Stays Current
Living codebase documentation rebuilds on every commit, scores its own freshness, and feeds AI agents. Learn how it works and start with repowise free.
Git Intelligence: Hotspots, Ownership & Coupling Explained
Git intelligence reads your git history to surface hotspots, code ownership, bus factor, and change coupling. Learn how the signals work and where to start.
How to Prioritize Technical Debt (Impact-per-Effort)
Prioritize technical debt by impact-per-effort: rank refactoring targets, find dead code, and read coverage as risk. Build your ranked worklist today.
Spotting Declining Code Health Trends Before They Bite
Declining code health is usually a slow-burn problem. Teams feel it as “everything takes longer” long before they see a hard failure. The trick is not…
Hidden Coupling: Finding the Files That Always Change Together
Hidden coupling is the code you do not see in imports. Two files have no direct dependency on paper, yet they still move together every few weeks because…
Nested Complexity vs Cyclomatic Complexity (and Why It Matters)
Nested complexity is the metric people reach for when cyclomatic complexity stops telling the truth. Cyclomatic complexity counts decision paths. Nested…
Refactoring Priorities: Picking What to Fix First
Most teams do not have a refactoring problem. They have a refactoring priorities problem. There is always more code that could be cleaned up than time to…
Untested Hotspots: The Highest-Leverage Coverage Targets
Untested hotspots are the files most likely to break your product and the least likely to catch it in CI. The signal is simple: high churn, low or zero…
What Is Code Health? A Practical Guide to the 21 Markers
What is code health? It is the part of a codebase that tells you whether the system will stay easy to change next week, next month, and next quarter. Code…
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.