rune

To sync local AI skills and agents with a remote registry, use a manifest-driven CLI workflow. Running operations like sync compares local items against the registry using a content-hash lockfile to ensure reproducible state and prevent drift.

Registry drift happens when local AI agent rules diverge from their remote source. It is tracked using a per-item content-hash lockfile and pedigree frontmatter that surface and record changes across multiple registry environments.

You can publish and import AI skills across multiple registries using the CLI-driven add and push operations. This manifest-driven workflow manages items end-to-end from a centralized configuration to ensure reproducible state.

Yes, you can use a manifest file to manage AI subagents across different environments. A rune.toml manifest provides centralized resolution to track skills, agents, and rules across varied local projects.

The best way to remove orphaned registry items from a local project is to run the prune CLI operation. This checks the manifest and deletes local files that no longer exist in the remote registry.

To initialize a lockfile to track changes to imported coding rules, run rune setup to install the hook and config, then run rune init in your project to create the rune.toml manifest and generate the content-hash lockfile.