byterover

Manages and queries project knowledge with a persistent, searchable context of user-defined choices.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/thenomadcode/Echo --skill byterover
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: byterover
Source: https://github.com/thenomadcode/Echo/tree/main/.opencode/skills/byterover
Command: npx skills add https://github.com/thenomadcode/Echo --skill byterover

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill helps manage and leverage project knowledge by providing a persistent context tree, allowing developers to query existing information and curate new learnings to avoid redundant work and capture insights.

Core Features & Use Cases

  • Query Knowledge: Retrieve information about patterns, conventions, and past decisions before starting work.
  • Curate Knowledge: Store insights, decisions, and bug fixes for future reference.
  • Use Case: Before implementing a new feature, query "How is authentication handled?" to understand existing patterns. After fixing a complex bug, curate "Root cause of X bug was Y, fixed by Z" with relevant file references.

Quick Start

Query ByteRover for information about how authentication is implemented in the project.

Frequently Asked Questions about byterover

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

FAQPage Schema
How do I manage project knowledge and retrieve past decisions across coding sessions?

Project knowledge management persists a context tree across sessions, letting you query existing patterns, conventions, and decisions, and curate new learnings with file references to avoid redundant work.

What is a context tree and how does it help with information retrieval in a codebase?

A context tree is a persistent structure for querying and curating codebase information. It retrieves existing patterns and conventions before starting work and stores new insights, decisions, and bug fixes for future reference.

How do I document a complex bug fix so the root cause is accessible later?

You curate knowledge by storing the root cause and fix details in the context tree with relevant file references. This captures the insight for future querying, preventing redundant debugging across development sessions.

Can I query existing conventions before implementing a new feature?

Yes, you query the context tree to retrieve information about existing patterns and conventions. For example, you can query how authentication is handled to understand established codebase patterns before starting work.

What's the best way to capture developer insights without disrupting the coding workflow?

Use a knowledge management skill to persist new learnings and file references directly in a context tree. It facilitates efficient development by providing quick access to stored decisions without disrupting workflow.