byterover

Query and curate persistent project knowledge via a ByteRover context tree.

16|12|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/AlekseiUL/heisenberg-team --skill byterover-alekseiul
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: byterover
Source: https://github.com/AlekseiUL/heisenberg-team/tree/main/skills/byterover
Command: npx skills add https://github.com/AlekseiUL/heisenberg-team --skill byterover-alekseiul

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Byterover helps you stop re-discovering project patterns and decisions by persisting knowledge that can be queried before work and curated after work.

Core Features & Use Cases

  • Query project knowledge: Retrieve prior conventions, decisions, and explanations before you start implementing or changing anything.
  • Curate new knowledge: Store fresh insights, bug root causes, and architecture decisions so the team’s future work starts informed.
  • Use it for knowledge persistence and pattern discovery: Best for “how does X work here?” questions, and for documenting what you learned once you fix or build something.

Quick Start

Run a knowledge lookup with brv query by asking a specific question about how a part of the codebase works, like brv query "How is auth implemented?".

Frequently Asked Questions about byterover

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I persist project knowledge across coding sessions?

You can persist project knowledge across coding sessions by using a context tree to retrieve prior conventions and curate new insights. This workflow ensures that architecture decisions and bug root causes remain accessible for future development tasks.

What is a retrieval-first workflow for project documentation?

A retrieval-first workflow for project documentation means querying existing context to understand how code works before implementing changes. This approach ensures you check prior conventions and explanations first, then document fresh insights after the work is complete.

How do I query existing architecture decisions before refactoring?

You query existing architecture decisions before refactoring by asking specific questions about codebase functionality. The system retrieves relevant patterns and explanations from the persistent context tree, keeping your refactoring efforts informed by past decisions.

Can I use file-scoped context ingestion for debugging knowledge management?

Yes, you can use file-scoped context ingestion for debugging knowledge management. This approach ensures that captured bug root causes and explanations remain specific to the relevant files, keeping the knowledge actionable and tightly coupled to your codebase.

Do I need YAML metadata to start capturing project learnings?

Yes, you need YAML metadata to start capturing project learnings. Defining a name and description in YAML is required for the operational support that enables querying and curating actions within your development workflow.

When should I not use a persistent context tree for pattern discovery?

You should not use a persistent context tree for pattern discovery if your work is strictly ephemeral and does not require durable knowledge capture. It is best suited for coding and architecture tasks where retrieving past decisions significantly informs future work.