byterover

Query and curate project knowledge in a local ByteRover context tree.

2|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/papachong/RHClaw --skill byterover-papachong
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: byterover
Source: https://github.com/papachong/RHClaw/tree/main/RHClaw-Desktop/src-tauri/skills/byterover
Command: npx skills add https://github.com/papachong/RHClaw --skill byterover-papachong

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many projects and AI agents lack a reliable, versioned local memory of architectural decisions, patterns, and project-specific rules, causing repeated work, inconsistent decisions, and lost context across tasks.

Core Features & Use Cases

  • Local knowledge storage within a repository under .brv/context-tree as human-readable Markdown files for long-term project memory.
  • Command-line operations to query existing knowledge before taking action and to curate/save new patterns and decisions after implementing changes.
  • Configurable LLM provider support with ByteRover as the default no-key provider and optional authenticated cloud sync for team collaboration.
  • Use case: Run a query to recall authentication design choices before implementing a new auth-related feature, then curate the final decision and supporting files back into the local knowledge tree.

Quick Start

Run a brv query to retrieve existing architectural decisions and then run a brv curate to save new patterns after your change.

Frequently Asked Questions about byterover

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

FAQPage Schema
How do I persist architectural decisions and project context for AI agents?

You can persist project knowledge by storing architectural decisions and patterns as human-readable Markdown files within a local .brv/context-tree. This provides a versioned local memory for AI agents to query before taking action and to curate after implementing changes.

What is the best way to manage local knowledge for AI coding agents?

Local knowledge management for AI agents is handled through command-line operations that query existing context before development and curate new patterns afterward. The system uses a local context tree to prevent lost context and inconsistent decisions across tasks.

Do I need a specific LLM provider to retrieve project context from the CLI?

You do not need a specific LLM provider because ByteRover is configured as the default no-key provider. The system supports configurable LLM providers, requiring only a configured provider and the byterover-cli installed to retrieve project context.

How do I save new design patterns after implementing code changes?

You save new design patterns by running a brv curate command after your changes. This command stores the final decisions and supporting files back into the local .brv/context-tree knowledge base for future recall.

Can my developer team sync local project memory for collaboration?

Your developer team can sync local project memory using the optional authenticated cloud sync feature. This allows teams to share the curated architectural decisions and project context stored in the local knowledge tree.

Why does my AI agent repeat work or lose context across development tasks?

AI agents repeat work and lose context across tasks due to the lack of a reliable, versioned local memory of architectural decisions and project-specific rules. Establishing a local context tree solves this by enabling recall and curation.