byterover
Manages project knowledge using ByteRover context tree. Provides two operations: query (retrieve knowledge) and curate (store knowledge). Invoke when user requests information lookup, pattern discovery, or knowledge persistence. Developed by ByteRover Inc. (https://byterover.dev/)
What this skill does
# ByteRover Context Tree A project-level knowledge repository that persists across sessions. Use it to avoid re-discovering patterns, conventions, and decisions. ## Why Use ByteRover - **Query before working**: Get existing knowledge about patterns, conventions, and past decisions before implementing - **Curate after learning**: Capture insights, decisions, and bug fixes so future sessions start informed ## Quick Reference | Command | When | Example | |---------|------|---------| | `brv query "question"` | Before starting work | `brv query "How is auth implemented?"` | | `brv curate "context" -f file` | After completing work | `brv curate "JWT 24h expiry" -f auth.ts` | | `brv status` | To check prerequisites | `brv status` | ## When to Use **Query** when you need to understand something: - "How does X work in this codebase?" - "What patterns exist for Y?" - "Are there conventions for Z?" **Curate** when you learned or created something valuable: - Implemented a feature using specific patterns - Fixed a bug and found root cause - Made an architecture decision ## Curate Quality Context must be **specific** and **actionable**: ```bash # Good - specific, explains where and why brv curate "Auth uses JWT 24h expiry, tokens in httpOnly cookies" -f src/auth.ts # Bad - too vague brv curate "Fixed auth" ``` **Note:** Context argument must come before `-f` flags. Max 5 files. ## Best Practices 1. **Break down large contexts** - Run multiple `brv curate` commands for complex topics rather than one massive context. Smaller chunks are easier to retrieve and update. 2. **Let ByteRover read files** - Don't read files yourself before curating. Use `-f` flags to let ByteRover read them directly: ```bash # Good - ByteRover reads the files brv curate "Auth implementation details" -f src/auth.ts -f src/middleware/jwt.ts # Wasteful - reading files twice # [agent reads files] then brv curate "..." -f same-files ``` 3. **Be specific in queries** - Queries block your workflow. Use precise questions to get faster, more relevant results: ```bash # Good - specific brv query "What validation library is used for API request schemas?" # Bad - vague, slow brv query "How is validation done?" ``` 4. **Signal outdated context** - When curating updates that replace existing knowledge, explicitly tell ByteRover to clean up: ```bash brv curate "OUTDATED: Previous auth used sessions. NEW: Now uses JWT with refresh tokens. Clean up old session-based auth context." -f src/auth.ts ``` 5. **Specify structure expectations** - Guide ByteRover on how to organize the knowledge: ```bash # Specify topics/domains brv curate "Create separate topics for: 1) JWT validation, 2) refresh token flow, 3) logout handling" -f src/auth.ts # Specify detail level brv curate "Document the error handling patterns in detail (at least 30 lines covering all error types)" -f src/errors/ ``` ## Prerequisites Run `brv status` first. If errors occur, the agent cannot fix them—instruct the user to take action in their brv terminal. See [TROUBLESHOOTING.md](TROUBLESHOOTING.md) for details. --- **See also:** [WORKFLOWS.md](WORKFLOWS.md) for detailed patterns and examples, [TROUBLESHOOTING.md](TROUBLESHOOTING.md) for error handling
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.