ByteRover Knowledge Audit

A structured workflow for auditing the health of your ByteRover knowledge base. Finds stale entries, missing coverage, and provides actionable remediation commands.

When to Use

• After major refactors or dependency upgrades
• Periodically (monthly or per sprint) to maintain knowledge quality
• When suspecting knowledge drift (documented patterns no longer match code)
• Before starting a new feature in an area with existing documentation

Prerequisites

Run brv status first. If errors occur, instruct the user to resolve them in the brv terminal. See the byterover skill's TROUBLESHOOTING.md for details.

Process

Phase 1: Inventory Existing Knowledge