Menü
Create scoped VCS snapshots from the current workspace state.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Draft release notes for Roder releases, new crates or packages, feature additions, behavior changes, and fixes. Use when writing release notes, changelog summaries, release announcements, or explaining what changed in a branch, PR, crate, SDK, or package release.
Use when editing TUI rendering code, adding new visible surfaces, or working on themes/CSS in Roder. Keeps class/id taxonomy, cascade order, and the supported CSS subset consistent across sessions.
Draft a changelog entry from the latest changes.
Use when a user asks for an orientation tour of an unfamiliar repository. Produces a structured tour of entry points, key modules, and how to run tests.
Use when a PR changes any released package (crates/*, sdk/typescript, sdk/python, packages/edit-tools), when the changeset-gate CI check fails, when adding a new crate or package to the release config, or when working on knope versioning/release automation. For the step-by-step workflow to add a change file, use $create-changeset.
Use when a PR or branch changes any released package (crates/*, sdk/typescript, sdk/python, packages/edit-tools), when the changeset-gate CI check fails, or before pushing work that touches versioned package directories. Creates the required .changeset/*.md file for knope per-package versioning.
| name | vcs-snapshot |
| description | Create scoped VCS snapshots from the current workspace state. |
| metadata | {"short-description":"Snapshot safely"} |
| exposure | direct_only |
Inspect VCS status and the relevant diff before creating a provider history snapshot.
Select only files or hunks that the user asked to include, if the active provider supports that granularity. Ignore unrelated changes from other agents unless the user explicitly asks to include them.
Write a concise snapshot message that reflects the saved behavior. In git workspaces this maps to a commit, so report the commit hash; for other providers, report the provider snapshot identity and the validation evidence used for the slice.
