byterover

Organize and persist cross-session project knowledge in a ByteRover context tree.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/Glour/ai-office-v2 --skill byterover-glour
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: byterover
Source: https://github.com/Glour/ai-office-v2/tree/main/skills/byterover
Command: npx skills add https://github.com/Glour/ai-office-v2 --skill byterover-glour

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ByteRover provides a persistent, project-wide knowledge repository that captures patterns, decisions, and conventions to prevent rework across sessions.

Core Features & Use Cases

  • Query: retrieve existing knowledge before starting work.
  • Curate: persist insights, decisions, and updates for future sessions.
  • Use Case: Onboarding a new team member by quickly surfacing architectural decisions and standards, or after a postmortem to capture lessons learned.

Quick Start

Initialize ByteRover in your workspace and begin querying or curating knowledge to build a shared, searchable context tree.

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 multiple coding sessions?

Team collaboration improves when you curate architectural standards and decisions into a shared context tree. Team members can query this repository during onboarding to quickly surface patterns and conventions without repeated explanations.

How do I manage postmortem knowledge for future software projects?

Querying existing knowledge before starting work requires a ByteRover context tree initialized in your workspace. You retrieve previously curated patterns and decisions to inform current tasks, preventing rework and ensuring consistency with project conventions.

Does project knowledge management work for onboarding new team members?

Yes, project knowledge management works for onboarding by allowing new team members to query a structured context tree. They can quickly surface architectural decisions, conventions, and standards, reducing ramp-up time and preventing inconsistent work patterns.

What is the best way to curate and retrieve project decisions across teams?

The best way to curate and retrieve project decisions is using a structured context tree that supports query and curate operations. This approach stores insights in a shared repository, enabling teams to load and reuse knowledge across multiple projects and sessions.