Visited Tracker Tools

Track code review coverage by logging file visits, exclusion rationales, and campaign notes. This prevents redundant work by clearly identifying which TypeScript, TSX, and Go files still need attention and which are already reviewed.

Find the least-visited files by invoking the visited-tracker least-visited command with your repository location and tag. This surfaces the next files based on staleness_score and visit_count to focus the next reviewer.

Yes, you can use glob-friendly file specifications when logging review coverage. The visit and exclude commands accept glob patterns, file notes, reasons, and coverage_percent guidance while keeping tags aligned per campaign.

Write handoff notes for code review campaigns using the campaigns note command. It captures completion share, remaining hotspots, and TODOs so teammates can pick up exactly where the last reviewer left off.

Coverage tracking works with TypeScript, TSX, and Go source files. It applies deterministic coverage reporting scoped by location and tag, ensuring consistent tracking across these specific file formats.

Logging exclusion rationales prevents redundant work by documenting why specific files were skipped. This ensures teams understand coverage gaps and avoids re-evaluating files that were intentionally excluded from the campaign.