V0: Revision History for Custom Skills
V0V0 added revision history for custom skills, letting teams see every past version of a skill along with the file paths, authors, and timestamps attached to each change. A built-in text diff view shows exactly what changed between revisions, making it easier to audit who modified a shared skill and why. The feature turns custom skills — which teams use to give V0 reusable, project-specific context — into something that can be reviewed and rolled back like any other piece of shared team infrastructure.
Key Takeaways
- Revision history now tracks every past change made to a custom skill, not just its current state.
- Each revision records the file path, author, and timestamp, giving teams a clear audit trail.
- A built-in text diff view highlights exactly what changed between two versions of a skill.
- The feature treats custom skills as shared team infrastructure rather than personal, unversioned files.
- It complements V0's existing custom skills system, which lets teams package reusable context and instructions for V0 to use across chats.
- The update shipped in V0's August 28, 2026 release alongside GPT-5.6 Sol model support and improved VM preview diagnostics.
Tracking Changes to Custom Skills
Custom skills let V0 teams package reusable instructions, context, and conventions that V0 draws on across chats — things like coding standards, brand guidelines, or integration patterns that would otherwise need to be repeated in every prompt. As more teams share skills across multiple people and projects, tracking who changed what, and when, became a real gap. V0's August 28, 2026 release addressed this by adding revision history to custom skills.
Each skill now keeps a history of its past versions, and every entry in that history records the file path that changed, the author who made the change, and the timestamp it happened. A text diff view lets anyone reviewing the history see precisely what was added, removed, or modified between two revisions, rather than having to compare full files by eye.
Why It Matters for Teams
This update effectively brings lightweight version control to a part of V0 that previously behaved more like a single, overwritable document. Teams that maintain shared skills — for example, a design-system skill referenced by every project, or an API-integration skill used across a company's chats — can now trace how that skill evolved, understand why a particular change was made, and identify who to ask if something breaks. It is a natural complement to V0's existing custom skills system and the disable-model-invocation and drag-to-reorder improvements shipped in earlier releases, continuing a broader trend of treating skills as first-class, collaboratively maintained assets rather than personal scratch files.