self-dev-loop

Files (1)

• SKILL.md

SKILL.md (first lines)

# Self-dev loop (Remedy on Remedy)

## Goal

One **ordered** playbook when the user wants Remedy to improve **this** monorepo
while staying a trustworthy partner. Prefer **activating sub-skills** rather than
re-inventing commands.

## When to use

- Working **in** the RemedyAI repo as the project  
- User says self-dev, dogfood loop, full quality loop, “run gauntlet then soak”  
- Multi-hour sessions that must not skip security or ship discipline  

## Default sequence

Execute **in order**. Skip a stage only if the user explicitly narrows scope
(e.g. “unit tests only”) or the stage does not apply (docs-only change).

```text
0. Orient        → project-overview / AGENTS.md / git status
1. Hot-inject    → self-inject (draft → test-gate → apply/rollback → restart)
2. Blast radius  → change-safety
3. Implement     → write-tests, refactor-safe as needed
4. Unit gates    → pytest + desktop npm test/build + check_docs
5. Gauntlet      → gauntlet-security (if security surface touched or user asked)
6. Soak          → soak-product (if desktop/API/CUA/stream touched or user asked)
7. Stress        → stress-suite (optional; after soak green or user asked)
8. Ship          → project-etiquette (test → docs → build → commit → CI → publish)
```

### Activate helpers

**Never** `skill_activate` every pack (“reload all skills”). That floods context
and causes endless tool loops. Rescan disk with:

```
skill_reload()
```

Then load **one** procedure at a time (or let auto-suggest inject for the task):

```
skill_activate(skill="self-dev-loop")   # this meta playbook
skill_activate(skill="self-inject")
skill_activate(skill="gauntlet-security")
skill_activate(skill="soak-product")
skill_activate(skill="stress-suite")
skill_activate(skill="change-safety")
skill_activate(skill="project-etiquette")
```

## Stage details (short)

### 0. Orient

```powershell
git status -sb
git log -5 --oneline
```

Read root `AGENTS.md` for ship gates, installer naming, smoke matrix.

### 1. Hot-inject

- **Draft** a change with normal edit tools (Python sidecar or desktop SPA).
- **Gate** is tests-only (pytest + npm test). Green → apply + restart sidecar /
  rebuild SPA; red → roll back and record in the ledger (`~/.remedy/self_inject_ledger.jsonl`).
- Full mechanics: `docs/SELF_INJECT.md`. Never commit red; never leave a broken tree.

### 2–3. Change + implement

- Name blast radius (chat, gateway, rails, settings, packaging).  
- Prefer durable fixes; keep tree runnable.  
- Pair with **write-tests** for behavior changes.

### 4. Unit gates (minimum always before ship)

```powershell
uv run pytest -q
cd desktop; npm test; npm run build
uv run python scripts/check_docs.py
```

### 5–7. Live quality (when scope needs it)

| Stage | Skill | Trigger |
|-------|--------|---------|
| Gauntlet | **gauntlet-security** | auth, jail, SSRF, host, sanitize |
| Soak | **soak-product** | CUA, browser, stream, multi-tab, “soak” |
| Stress | **stress-suite** | concurrency, multi-provider, “stress/break” |

Set `REMEDY_API` / `REMEDY_HOME` to the profile under test.

### 8. Ship

Follow **project-etiquette** exactly: no publish on red CI; version only for real
releases; desktop tag `vX.Y.Z` for installers.

## Reporting template

| Stage | Result | Evidence |
|-------|--------|----------|
| Hot-inject | applied / rolled back / n/a | ledger + diff-id |
| Blast radius | surfaces listed | |
| Unit | pass/fail | commands |
| Gauntlet | pass/fail/skip | |
| Soak | pass/fail/skip | `docs/_full_product_soak_results.json` |
| Stress | pass/fail/skip | |
| Ship | commit / CI / publish | |

## Anti-patterns

- Stress before unit green  
- Gauntlet against the wrong API port/home  
- Shipping without **project-etiquette** when user asked for release  
- Dual messenger pollers "for testing"  
- Committing a **red** self-inject round (never — roll back instead)  
- Claiming self-dev done when only the chat replied and no commands ran

From AhmiDarrow/RemedyAI, Apache-2.0.

More from AhmiDarrow/RemedyAI