Skip to content

Updating and pinning

Terminal window
quiver update # every source
quiver update anthropic # some sources

For each source, quiver update first downloads the new commits without applying them, and lists the skills that would be added, changed or removed. For each assigned skill that changes, it lists the changed files, and marks scripts, such as .sh, .py and .js files and executable files, as needs review: the assistant may run them.

When an assigned skill would change or go away, it asks before it applies the changes. Answering no leaves the source as it was. Changes to skills that are not assigned are applied right away. Pinned skills are left alone.

FlagEffect
--diffShow the whole change of each assigned skill that changes.
--yesApply the changes without asking.
--resetTake the remote history of a source that was force-pushed.

A source whose history was rewritten is not updated until you run it with --reset.

A skill folder in a source that is a symlink is not discovered, so an update cannot change a skill through files that git reports somewhere else. quiver source add prints a warning for each one it skips.

A pin keeps a source skill at one commit, so its text changes only when you decide:

Terminal window
quiver pin anthropic/pdf # at the source's current commit
quiver pin acme/review 3f2a9c1 # at a given hash, tag or branch

The pin applies everywhere the skill is assigned, and the skill keeps its ID. The pinned commit is checked out into ~/.quiver/sources/.pins; an older commit is downloaded first when needed.

To review changes before they reach your sessions: pin the skill, read the changes with quiver update --diff, then move the pin to the new commit.

Terminal window
quiver unpin anthropic/pdf # serve the source's current version again

Source skills are read-only. To change one, copy it into your own skills:

Terminal window
quiver fork anthropic/pdf
quiver fork acme/review --as team-review

The copy is named after the skill, or --as. Its frontmatter records where it came from, as forkedFrom: <id>@<commit>. Wherever the original is assigned, globally or in a project, the copy takes its place, always-on marks included.

From then on quiver edit changes what those projects get, and quiver update no longer does.