vcs

Automate version control workflows using JJ commands for history, diffs, and commits.

2|Updated Mar 16, 2021
One-click install
npx skills add https://github.com/karitham/dotfiles --skill vcs-karitham
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vcs
Source: https://github.com/karitham/dotfiles/tree/main/modules/opencode/skills/vcs
Command: npx skills add https://github.com/karitham/dotfiles --skill vcs-karitham

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

JJ provides a streamlined version-control workflow using the JJ tool, replacing Git's model with JJ's commit-centric approach and built-in history, diff, and status operations, enabling quicker history review and safer collaboration.

Core Features & Use Cases

  • View history: Use jj log to see the project history across revisions.
  • Inspect files at revisions: Use jj file show <revision>:<path> to view specific versions.
  • Compare changes & check status: Use jj diff and jj st to review modifications and the current state.
  • Commit changes safely: Use jj commit to finalize changes with descriptive messages.

Quick Start

View history with jj log, inspect changes with jj file show, and commit with jj commit -m 'your message'.

Frequently Asked Questions about vcs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review project history and inspect file changes using JJ?

To review project history with JJ, run jj log to see revisions, then use jj file show <revision>:<path> to inspect specific file versions and compare changes across your commit history.

What's the best way to commit changes in a JJ-based version control workflow?

The best way to commit changes in a JJ workflow is using jj commit -m 'your message', which safely finalizes modifications with descriptive messages after reviewing them with jj diff and jj st.

Can I use JJ as a Git alternative for reviewing diffs and checking status?

Yes, you can use JJ as a Git alternative for reviewing diffs and checking status. JJ provides built-in operations like jj diff to review modifications and jj st to track the current state.

Does the vcs Skill require any specific version control tooling to run?

Yes, the vcs Skill requires JJ tooling to function. It uses specific JJ commands including jj log, jj diff, jj st, jj file show, and jj commit to perform end-to-end version control operations.

How does JJ's commit-centric approach differ from Git for version control?

JJ's commit-centric approach streamlines version control by replacing Git's model with built-in history, diff, and status operations, enabling quicker history review and safer collaboration without traditional Git branching overhead.

Why use JJ file show instead of standard diff commands to inspect past revisions?

You use jj file show <revision>:<path> to view specific versions of files at exact revisions. This targeted inspection allows precise historical tracking that standard diff commands do not directly offer.