@revotools/cli 0.2.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 dean0x
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,198 @@
+# Revo
+
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
+
+Claude-first multi-repo workspace manager.
+
+Revo is a fork of [Mars](https://github.com/dean0x/mars). It keeps everything
+Mars gives you — tag-based filtering, coordinated branches, zero dependencies —
+and adds features designed for working with coding agents:
+
+- **`revo context`** scans your repos and writes a root-level `CLAUDE.md` so
+  Claude Code can understand the whole workspace at a glance.
+- **`revo feature <name>`** creates a coordinated branch and shared context
+  file across matching repos.
+- **`revo commit`**, **`revo push`**, **`revo pr`** let you commit, push, and
+  open PRs across the stack in one step.
+- **`depends_on`** in `revo.yaml` feeds a topological sort into the generated
+  CLAUDE.md so the agent knows what to change first.
+
+Pure bash 3.2+, works on macOS out of the box, no runtime dependencies beyond
+`git` (and optionally `gh` for `revo pr`).
+
+## Quick Start
+
+```bash
+mkdir my-project && cd my-project
+revo init
+
+revo add git@github.com:org/shared-types.git --tags shared
+revo add git@github.com:org/backend.git --tags backend,api --depends-on shared-types
+revo add git@github.com:org/frontend.git --tags frontend,web --depends-on backend
+
+revo clone            # CLAUDE.md is auto-generated after first clone
+revo context          # regenerate it any time repos change
+```
+
+Then point Claude Code at the workspace directory and it will read `CLAUDE.md`
+on its own.
+
+## Claude Code Workflow
+
+```
+revo init
+  ↓
+revo add (repos, with --depends-on)
+  ↓
+revo clone                         ── auto-generates CLAUDE.md
+  ↓
+Claude Code reads CLAUDE.md
+  ↓
+revo feature clock-student         ── branch + .revo/features/clock-student.md
+  ↓
+Claude Code works across repos
+  ↓
+revo commit "wire up clock endpoint"
+  ↓
+revo push
+  ↓
+revo pr "Clock endpoint for students"    ── coordinated PRs via gh
+```
+
+## Commands
+
+### Workspace (from Mars)
+
+| Command | Description |
+|---------|-------------|
+| `revo init` | Initialize a new workspace |
+| `revo add <url> [--tags t1,t2] [--depends-on r1,r2]` | Add a repository to config |
+| `revo clone [--tag TAG]` | Clone configured repositories |
+| `revo list [--tag TAG]` | List configured repositories |
+| `revo status [--tag TAG]` | Show status of all repositories |
+| `revo sync [--tag TAG] [--rebase]` | Pull latest changes |
+| `revo branch <name> [--tag TAG]` | Create branch on repositories |
+| `revo checkout <branch> [--tag TAG]` | Checkout branch on repositories |
+| `revo exec "<cmd>" [--tag TAG]` | Run command in each repository |
+
+### Claude-first (new in Revo)
+
+| Command | Description |
+|---------|-------------|
+| `revo context` | Scan repos and regenerate workspace `CLAUDE.md` |
+| `revo feature <name> [--tag TAG]` | Coordinated feature branch + `.revo/features/<name>.md` |
+| `revo commit <msg> [--tag TAG]` | Commit across dirty repos |
+| `revo push [--tag TAG]` | Push branches across repos |
+| `revo pr <title> [--tag TAG] [--body BODY]` | Create coordinated PRs via `gh` |
+
+## Tag Filtering
+
+Target subsets of repos using `--tag`:
+
+```bash
+# Only clone frontend repos
+revo clone --tag frontend
+
+# Create coordinated feature on backend repos only
+revo feature auth-overhaul --tag backend
+
+# Run npm install on all frontend repos
+revo exec "npm install" --tag frontend
+```
+
+## Configuration
+
+### revo.yaml
+
+```yaml
+version: 1
+
+workspace:
+  name: "my-project"
+
+repos:
+  - url: git@github.com:org/shared-types.git
+    tags: [shared, types]
+
+  - url: git@github.com:org/backend.git
+    path: api                     # optional custom path
+    tags: [backend, api]
+    depends_on: [shared-types]    # optional — drives dep order in CLAUDE.md
+
+  - url: git@github.com:org/frontend.git
+    tags: [frontend, web]
+    depends_on: [backend]
+
+defaults:
+  branch: main
+```
+
+`depends_on` references repos by their path basename (the bit derived from
+the URL, or the explicit `path` if set).
+
+Migrating from Mars? `mars.yaml` is still honored as a fallback, so `revo`
+works in existing Mars workspaces without renaming anything.
+
+## Workspace Structure
+
+```
+my-project/
+├── revo.yaml           # Workspace configuration
+├── CLAUDE.md           # Auto-generated by revo context
+├── .gitignore          # Contains 'repos/' and '.revo/'
+├── .revo/              # Revo-local state (gitignored)
+│   └── features/       # Feature context files
+│       ├── clock-student.md
+│       └── auth-overhaul.md
+└── repos/              # Cloned repositories (gitignored)
+    ├── shared-types/
+    ├── backend/
+    └── frontend/
+```
+
+## Why not...
+
+- **...a monorepo?** Because these repos are real, separately owned codebases
+  with their own CI, deploys, and histories. A monorepo forces a reorg Revo
+  doesn't need.
+- **...plain sibling directories?** Because you lose tag filtering, coordinated
+  branches, coordinated PRs, and — most importantly — a shared `CLAUDE.md`
+  that the agent can actually read.
+- **...a bespoke orchestrator?** Because Revo does nothing at runtime. It
+  doesn't build, deploy, or test. It just shapes the workspace.
+
+## Installation
+
+### Manual (recommended while pre-release)
+
+```bash
+git clone https://github.com/marcus.salinas/revo.git
+cd revo
+./build.sh
+cp dist/revo ~/.local/bin/  # or anywhere in PATH
+```
+
+### Shell Script
+
+```bash
+curl -fsSL https://raw.githubusercontent.com/marcus.salinas/revo/main/install.sh | bash
+```
+
+### npm
+
+```bash
+npm install -g revo-cli
+```
+
+## Contributing
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for development setup, architecture, and release process.
+
+## Credits
+
+Revo is a fork of [Mars](https://github.com/dean0x/mars) by [@dean0x](https://github.com/dean0x).
+The workspace layer is Mars's work; Revo adds the Claude-first commands on top.
+
+## License
+
+MIT