agentsuser-updatelisted

# /agents user update Open `.agent-user.md` in the user's IDE for a manual edit, then validate against the locked v1 schema on save. Use when: - The user knows exactly what they want to change (nickname, language, voice sample) and doesn't need the interview flow. - The user wants to edit the freeform `# Notes` body. - `/agents user show` flagged a malformed field. For agent-driven changes from buffered observations, use [`/agents user review`](review.md) → [`/agents user accept`](accept.md). ## Steps ### 1. Precondition ```bash ls .agent-user.md 2>/dev/null ``` Missing → print "No `.agent-user.md` found. Run `/agents user init` first." and stop. ### 2. Open in IDE Use the [`file-editor`](../../../../dist/agent-src/skills/file-editor/SKILL.md) skill — reads `personal.ide` from `.agent-settings.yml` (vscode, phpstorm, cursor, etc.) and opens the file. If `personal.ide` is unset or `auto_open_files: false`, print: ``` ℹ️ Open .agent-user.md in your editor and re-run /agents user update --validate when done. ``` ### 3. Wait for save → validate When called with `--validate` (or after the user confirms "done"): 1. Read `.agent-user.md`. 2. Parse frontmatter; check every required field per [`agent-user-schema § Field reference`](../../../../docs/contracts/agent-user-schema.md#field-reference). 3. Check file size ≤100 lines. 4. Run the privacy-floor scan (same as `init` step 4): credentials, third-party PII, financial figures, health/legal status. | Result |