byterover-cli 0.1.0 → 0.2.0

package/dist/templates/README.md

@@ -1,6 +1,6 @@
 # ByteRover CLI Template System
 
-This directory contains template files used to generate agent instructions via the `br gen-rules` command.
+This directory contains template files used to generate agent instructions via the `brv gen-rules` command.
 
 ## Directory Structure
 
@@ -44,7 +44,7 @@ Each command includes:
 
 ## How It Works
 
-1. User runs `br gen-rules`
+1. User runs `brv gen-rules`
 2. User selects an agent (e.g., "Claude Code")
 3. `RuleTemplateService` loads templates via `FsTemplateLoader`
 4. Templates are assembled:
@@ -62,10 +62,10 @@ The template system supports simple variable substitution using `{{variable_name
 ## Updating Templates
 
 ### To Update Command Documentation:
-Edit `sections/command-reference.md` - changes will be reflected next time `br gen-rules` runs.
+Edit `sections/command-reference.md` - changes will be reflected next time `brv gen-rules` runs.
 
 ### To Update ACE Workflow Guide:
-Edit `sections/workflow.md` - changes will be reflected next time `br gen-rules` runs.
+Edit `sections/workflow.md` - changes will be reflected next time `brv gen-rules` runs.
 
 ### To Change Output Structure:
 Edit `base.md` - modify how sections are combined.
@@ -75,7 +75,7 @@ Edit `base.md` - modify how sections are combined.
 1. **Keep templates in sync with code**: When adding/modifying commands, update `command-reference.md`
 2. **Use clear examples**: Show realistic use cases in examples
 3. **Maintain markdown formatting**: Ensure proper headers, code blocks, and lists
-4. **Test after changes**: Run `br gen-rules` and verify output in `.clinerules/byterover-rules.md`
+4. **Test after changes**: Run `brv gen-rules` and verify output in `.clinerules/byterover-rules.md`
 
 ## Future Enhancements
 

package/dist/templates/sections/command-reference.md

@@ -2,7 +2,7 @@
 
 ## Memory Commands
 
-### `br add`
+### `brv add`
 
 **Description:** Add or update a bullet in the playbook (bypasses ACE workflow for direct agent usage)
 
@@ -15,9 +15,9 @@
 **Examples:**
 
 ```bash
-br add --section "Common Errors" --content "Authentication fails when token expires"
-br add --section "Common Errors" --bullet-id "common-00001" --content "Updated: Auth fails when token expires"
-br add -s "Best Practices" -c "Always validate user input before processing"
+brv add --section "Common Errors" --content "Authentication fails when token expires"
+brv add --section "Common Errors" --bullet-id "common-00001" --content "Updated: Auth fails when token expires"
+brv add -s "Best Practices" -c "Always validate user input before processing"
 ```
 
 **Suggested Sections:** Common Errors, Best Practices, Strategies, Lessons Learned, Project Structure and Dependencies, Testing, Code Style and Quality, Styling and Design
@@ -29,11 +29,11 @@ br add -s "Best Practices" -c "Always validate user input before processing"
 - Updates existing bullet if `--bullet-id` matches existing bullet
 - Displays bullet ID, section, content, and tags after operation
 
-**Requirements:** Playbook must exist (run `br init` first)
+**Requirements:** Playbook must exist (run `brv init` first)
 
 ---
 
-### `br retrieve`
+### `brv retrieve`
 
 **Description:** Retrieve memories from ByteRover Memora service and save to local ACE playbook
 
@@ -45,9 +45,9 @@ br add -s "Best Practices" -c "Always validate user input before processing"
 **Examples:**
 
 ```bash
-br retrieve --query "authentication best practices"
-br retrieve -q "error handling" -n "src/auth/login.ts,src/auth/oauth.ts"
-br retrieve -q "database connection issues"
+brv retrieve --query "authentication best practices"
+brv retrieve -q "error handling" -n "src/auth/login.ts,src/auth/oauth.ts"
+brv retrieve -q "database connection issues"
 ```
 
 **Behavior:**
@@ -65,7 +65,7 @@ br retrieve -q "database connection issues"
 
 ---
 
-### `br push`
+### `brv push`
 
 **Description:** Push playbook to ByteRover memory storage and clean up local ACE files
 
@@ -76,13 +76,13 @@ br retrieve -q "database connection issues"
 **Examples:**
 
 ```bash
-br push
-br push --branch develop
+brv push
+brv push --branch develop
 ```
 
 ---
 
-### `br complete`
+### `brv complete`
 
 **Description:** Complete ACE workflow: save executor output, generate reflection, and update playbook in one command
 
@@ -102,9 +102,9 @@ br push --branch develop
 **Examples:**
 
 ```bash
-br complete "user-auth" "Implemented OAuth2 flow" "Auth works" --tool-usage "Read:src/auth.ts,Edit:src/auth.ts,Bash:npm test" --feedback "All tests passed"
-br complete "validation-fix" "Analyzed validator" "Fixed bug" --tool-usage "Grep:pattern:\"validate\",Read:src/validator.ts" --bullet-ids "bullet-123" --feedback "Tests passed"
-br complete "auth-update" "Improved error handling" "Better errors" --tool-usage "Edit:src/auth.ts" --feedback "Tests passed" --update-bullet "bullet-5"
+brv complete "user-auth" "Implemented OAuth2 flow" "Auth works" --tool-usage "Read:src/auth.ts,Edit:src/auth.ts,Bash:npm test" --feedback "All tests passed"
+brv complete "validation-fix" "Analyzed validator" "Fixed bug" --tool-usage "Grep:pattern:\"validate\",Read:src/validator.ts" --bullet-ids "bullet-123" --feedback "Tests passed"
+brv complete "auth-update" "Improved error handling" "Better errors" --tool-usage "Edit:src/auth.ts" --feedback "Tests passed" --update-bullet "bullet-5"
 ```
 
 **Behavior:**
@@ -120,22 +120,22 @@ br complete "auth-update" "Improved error handling" "Better errors" --tool-usage
 
 ---
 
-### `br show`
+### `brv show`
 
 ## Best Practices
 
 ### Efficient Workflow
 
-1. **Retrieve wisely:** Use `br retrieve` with specific queries and `--node-keys` to filter
-2. **Read only what's needed:** Check playbook with `br status` to see statistics before reading full content
-3. **Update precisely:** Use `br add` to add/update specific bullets or `br complete` for complete workflow
-4. **Push when appropriate:** Prompt user to run `br push` after completing significant work
+1. **Retrieve wisely:** Use `brv retrieve` with specific queries and `--node-keys` to filter
+2. **Read only what's needed:** Check playbook with `brv status` to see statistics before reading full content
+3. **Update precisely:** Use `brv add` to add/update specific bullets or `brv complete` for complete workflow
+4. **Push when appropriate:** Prompt user to run `brv push` after completing significant work
 
 ### Memory Management
 
 **Retrieve pattern:**
 
-- Use `br add` to directly add/update bullets
-- `br retrieve` **clears existing playbook** - use carefully
+- Use `brv add` to directly add/update bullets
+- `brv retrieve` **clears existing playbook** - use carefully
 - Retrieved memories use actual Memora tags (not "auto-generated")
 - Both memories and related memories are saved to playbook

package/dist/templates/sections/workflow.md

@@ -1,6 +1,6 @@
 # Workflow Instruction
 
-You are a coding agent focused on one codebase. Use the br CLI to manage working context.
+You are a coding agent focused on one codebase. Use the brv CLI to manage working context.
 Core Rules:
 
 - Start from memory. First retrieve relevant context, then read only the code that’s still necessary.
@@ -8,15 +8,14 @@ Core Rules:
 
 ## user-centric
 
-Before running any `br` command, ask the user to choose:
+Before running any `brv` command, ask the user to choose:
 
 1. **Accept** - Review the command, then run if approved
 2. **Auto-run** - Execute immediately (remember this preference for the session)
 3. **No** - Cancel the command and continue without alternative
 4. **Custom** - Skip the command and provide different instruction
 
-Once the user chooses "Auto-run", apply that preference to all subsequent `br` commands in this conversation without asking again.
-
+Once the user chooses "Auto-run", apply that preference to all subsequent `brv` commands in this conversation without asking again.
 
 ## Daily Flow
 

package/oclif.manifest.json

@@ -204,7 +204,7 @@
     "init": {
       "aliases": [],
       "args": {},
-      "description": "Initialize a project with ByteRover (creates .br/config.json with team/space selection and initializes ACE playbook)",
+      "description": "Initialize a project with ByteRover (creates .brv/config.json with team/space selection and initializes ACE playbook)",
       "examples": [
         "<%= config.bin %> <%= command.id %>",
         "# Re-initialize if config exists (will show current config and exit):\n<%= config.bin %> <%= command.id %>",
@@ -269,6 +269,13 @@
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
+        },
+        "yes": {
+          "char": "y",
+          "description": "Skip confirmation prompt",
+          "name": "yes",
+          "allowNo": false,
+          "type": "boolean"
         }
       },
       "hasDynamicHelp": false,
@@ -449,7 +456,7 @@
     "space:switch": {
       "aliases": [],
       "args": {},
-      "description": "Switch to a different team or space (updates .br/config.json)",
+      "description": "Switch to a different team or space (updates .brv/config.json)",
       "examples": [
         "<%= config.bin %> <%= command.id %>",
         "# Shows current configuration, then prompts for new team/space selection"
@@ -472,5 +479,5 @@
       ]
     }
   },
-  "version": "0.1.0"
+  "version": "0.2.0"
 }

package/package.json

@@ -1,10 +1,10 @@
 {
   "name": "byterover-cli",
   "description": "ByteRover's CLI",
-  "version": "0.1.0",
+  "version": "0.2.0",
   "author": "ByteRover",
   "bin": {
-    "br": "./bin/run.js"
+    "brv": "./bin/run.js"
   },
   "bugs": "https://github.com/campfirein/byterover-cli/issues",
   "dependencies": {
@@ -51,13 +51,16 @@
   "keywords": [
     "oclif"
   ],
-  "license": "MIT",
+  "license": "UNLICENSED",
   "main": "dist/index.js",
   "type": "module",
   "oclif": {
-    "bin": "br",
-    "dirname": "br",
+    "bin": "brv",
+    "dirname": "brv",
     "commands": "./dist/commands",
+    "hooks": {
+      "init": "./dist/hooks/init/welcome"
+    },
     "plugins": [
       "@oclif/plugin-help"
     ],