Dayarc Upgrade

Files (1)

• SKILL.md

SKILL.md (first lines)

## When to Use

User asks to update, upgrade, or check for new versions of the agent — including upgrading to a specific branch or commit, or returning to stable `main`.

## Detecting Install Method

First, determine how Dayarc was installed:

```powershell
# Check plugin install
$pluginHit = Get-ChildItem -Path (Join-Path $HOME ".copilot\installed-plugins") -Filter "plugin.json" -Recurse -ErrorAction SilentlyContinue | Where-Object {
    (Get-Content $_.FullName -Raw | ConvertFrom-Json).name -eq "dayarc"
} | Select-Object -First 1

# Check git clone
$cloneDir = Join-Path $HOME ".dayarc-agent"
$isClone = Test-Path (Join-Path $cloneDir ".git")
```

- **Plugin install** → `$pluginHit` exists → use `copilot plugin update dayarc`
- **Git clone** → `$isClone` is true → use git-based upgrade (below)
- **Neither found** → tell user to reinstall

## Plugin Upgrade

If installed as a plugin, **do not run the upgrade yourself.** Plugin upgrades are managed by the Copilot CLI's built-in slash command, which only the user can invoke from chat. Instruct the user:

> To upgrade the Dayarc plugin, run `/plugin update dayarc` in this chat. Once it finishes, ask me again and I'll re-register the scheduler if needed.

If the user reports the slash command has completed, run the **After Update** scheduler re-registration steps (skip the file-copy step — the plugin system handles that).

**Preview branches are not supported for plugin installs.** If the user asks for a preview branch, tell them to use the git clone install method instead.

## Git Clone Upgrade

### Detecting Preview Mode

Check whether `~/.dayarc-agent/.preview` exists. If it does, warn the user:

> ⚠️ **Preview build active** — you are running a pre-release commit (`<contents of .preview>`). This build may be unstable. Say *"upgrade to stable"* to return to `main`.

### Check for Updates

```
cd ~/.dayarc-agent
git fetch origin main
```

Compare `HEAD` vs `origin/main`:
- If identical → "Already up to date."
- If behind → show new commits: `git log HEAD..origin/main --oneline`

### Apply Update (stable, default)

```
git pull --ff-only origin main
```

If fast-forward fails (local modifications), tell the user:
> Local changes detected. Run `irm https://raw.githubusercontent.com/YuiZhou/dayarc-agent/main/setup.ps1 | iex` to reinstall cleanly.

After a successful stable update, if `~/.dayarc-agent/.preview` exists, delete it.

### Preview Upgrade (branch or commit)

Triggered when the user says something like:
- *"upgrade to branch feat/triage-bot"*
- *"upgrade to commit abc1234"*
- *"preview branch feat/new-feature"*

Steps:

1. **Warn** the user upfront:
   > ⚠️ Preview builds may be unstable and are not suitable for production use. Proceed?

   Wait for explicit confirmation ("yes" / "ok" / "proceed"). If the user does not confirm, abort.

2. **Guard local changes** — stash any uncommitted changes first:
   ```powershell
   cd ~/.dayarc-agent
   git stash --include-untracked
   ```
   Note the stash result. If the working tree is clean, note that too (nothing to stash).

3. **Fetch the ref**:
   ```powershell
   git fetch origin <branch-or-sha>
   ```
   If the ref looks like a branch name (not a 40-char or abbreviated hex SHA), fetch it as:
   ```powershell
   git fetch origin refs/heads/<branch>:refs/remotes/origin/<branch>
   ```

4. **Resolve to a commit SHA**:
   ```powershell
   git rev-parse FETCH_HEAD
   ```

5. **Detach HEAD to that commit**:
   ```powershell
   git checkout --detach FETCH_HEAD
   ```

6. **Write the `.preview` marker** with the ref description and resolved SHA:
   ```
   feat/triage-bot @ abc1234f
   ```
   Full path: `~/.dayarc-agent/.preview`

7. **Run After Update steps** (copy files, re-register scheduler if applicable).

8. **Report**:
   > ✅ Now running preview: `feat/triage-bot @ abc1234f`. Say *"upgrade to stable"* to return to `main`.

If `git fetch` or `git checkout` fails (e.g., invalid ref), tell the user the ref could not be found and abort without modifying any files.

### Return to Stable

Triggered when the user says *"upgrade to stable"*, *"rollback"*, or *"go back to main"*.

From YuiZhou/dayarc-agent, MIT.

More from YuiZhou/dayarc-agent