walter-worker-fix

Files (1)

• SKILL.md

SKILL.md (first lines)

# walter-worker-fix

Fix issues in the walter-worker project source code, run tests, commit, push, then invoke `walter-worker-upgrade` to distribute the fix.

## Workflow

### 1. Analyze

Determine if the issue is in walter-worker source code — not just a usage or config problem.

Indicators:
- Bug in `setup/install.sh`, `src/coworker/`, templates (`src/coworker/templates/`), or skills (`skills/`)
- Behavior that affects ALL projects (global config, hooks, CLAUDE.md generation)
- Skill produces wrong output due to bad instructions
- Config/settings are corrupted because walter-worker wrote wrong values

If the issue is NOT in walter-worker code, report it as a separate issue and stop here.

### 2. Fix

Edit the walter-worker source files. Follow project conventions:
- Match existing code style
- Update design docs and blueprint alongside code changes
- No speculative changes, no unrelated refactoring

### 3. Verify

Run tests and ensure nothing breaks:
```bash
python -m pytest tests/ -x -q
```

Also verify the install script is valid:
```bash
bash setup/install.sh --dry-run 2>&1 || true
```

### 4. Commit & Push

```bash
git add -A
git diff --cached --stat
git commit -m "fix: {desc}"
git push origin main
```

### 5. Distribute

Invoke the `walter-worker-upgrade` skill to apply the fix to all projects and IDE configs. This pulls latest code, merges CLAUDE.md, installs skills, and syncs configs.

## Rules

- Only fix walter-worker code — don't fix symptoms in individual project configs
- Always run tests before committing
- Always push before upgrading (upgrade pulls from remote)
- If tests fail, loop: fix → verify → retry until all pass
- Keep commits focused on one fix at a time

From cicidi/walter-worker, MIT.

More from cicidi/walter-worker