chenxin-yan/gyst/gyst-refresh

Update a walkthrough

Load the gyst skill's planning, authoring and publication rules as reference; continue the existing session rather than starting its workflow.

1. Choose the snapshot

Take the session id from the conversation, or from gyst session list for this repository and the scope under discussion; ask if several match. Read gyst session status --session <id>; record the scope, revision, groups and Viewed hunks. Pass --session <id> to every subsequent command. If no session exists, direct the user to gyst and stop. Ask before changing scope.

A source-change notice alone calls for informing the user and asking whether to refresh.

2. Reconcile and publish

Reread status and gyst session diff --session <id>. Reassess affected code and tests. Refresh keeps surviving groups, their overviews and order, and a hunk's Viewed only when it matches exactly. A new snapshot drops every note; reauthor notes against the new snapshot rather than reattaching old ones by proximity. Plan coverage for every current hunk while preserving unrelated groups and their order.

Revise affected groups with group.update (optional title, overview, memberHunkIds, files) and their notes with note.create, note.update and note.remove by id, or dissolve/create groups to split or merge them. Follow gyst's atomic publication and retry rules. Explain restructuring; avoid no-op updates.

3. Hand back

Verify every current hunk belongs to a group, or report the remaining ungrouped hunks or blocker. Summarize what refreshed, which groups changed, preserved progress and what needs re-review. The open TUI updates without restarting.