Skip to content

Commit c8ae461

Browse files
committed
Add upgrade-run402 Codex skill
1 parent ed1aea1 commit c8ae461

2 files changed

Lines changed: 29 additions & 0 deletions

File tree

.claude/commands/upgrade-run402.md

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,33 @@
11
Check what's changed in the private run402 repo since the last sync and determine if any changes need to flow into run402-public (CLI, MCP, or OpenClaw skill).
22

3+
## Step 0: Update the private repo first
4+
5+
Before reading logs or classifying anything, make sure `~/Developer/run402-private` is current with its upstream:
6+
7+
```bash
8+
cd ~/Developer/run402-private
9+
git fetch origin
10+
git status --short
11+
git rev-list --left-right --count HEAD...origin/main
12+
```
13+
14+
If local `main` is behind `origin/main`, pull before continuing:
15+
16+
```bash
17+
cd ~/Developer/run402-private
18+
git pull --ff-only --autostash
19+
git rev-parse HEAD
20+
git rev-parse origin/main
21+
```
22+
23+
Continue only when `HEAD` equals `origin/main`. If the pull is blocked by local changes, untracked files, or an autostash conflict, stop and report:
24+
- the current `HEAD`
25+
- the `origin/main` commit
26+
- the ahead/behind count
27+
- the paths blocking the pull
28+
29+
Do **not** classify stale local commits as the latest private updates. If the repo cannot be pulled cleanly, the upgrade report must say that the private checkout is not current and no conclusions were made from stale `HEAD`.
30+
331
## Step 1: Find the sync point
432

533
Read the memory file `project_last_integration.md` to get the last known sync commits. If no memory exists, fall back to comparing recent git logs in both repos to find the divergence point.
Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
../../../.claude/commands/upgrade-run402.md

0 commit comments

Comments
 (0)