Token导航 LogoToken导航

Agent Skill · 运维和基础设施

jj-vcs(杰杰 VCS)

jj-vcs 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

jj-vcs 是运维和基础设施类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为执行命令;许可证为 MIT,第三方扫描已通过,按安装量在运维和基础设施类的 2,449 个 Skill 里排第 1,124。

总安装 865周安装 35GitHub Stars 1下载 272核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:jj-vcs(杰杰 VCS)
来源仓库:https://github.com/seckatie/katies-ai-skills
仓库路径:skills/jj-vcs
安装命令:
npx skills add https://github.com/seckatie/katies-ai-skills --skill jj-vcs
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/seckatie/katies-ai-skills --skill jj-vcs

这个 Skill 是做什么的

运维和基础设施类 Skill 处理部署、监控、日志和云资源,多数需要较高的执行权限。

用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息。适合围绕仓库状态、代码变更或协作事项进行整理和辅助分析。可结合来源仓库和 README 进一步验证实际用途和限制。

安装命令:npx skills add https://github.com/seckatie/katies-ai-skills --skill jj-vcs。注意权限范围和维护状态,避免触发联网、命令执行或文件读写。

来源仓库内路径:skills/jj-vcs

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/seckatie/katies-ai-skills --skill jj-vcs;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要执行命令,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

jj-vcs 怎么安装?

在终端执行 npx skills add https://github.com/seckatie/katies-ai-skills --skill jj-vcs。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

jj-vcs 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

jj-vcs 需要什么权限?

权限级别是执行命令。安装流程涉及命令执行,可能通过 npx skills add https://github.com/seckatie/katies-ai-skills --skill jj-vcs;npx skills add seckatie/katies-ai-skills --skill "jj-vcs" 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

jj-vcs 是免费的吗?

来源标注的许可证是 MIT。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

jj-vcs 用的人多吗?

公开数据是累计安装 865 次,近一周安装 35 次,下载 272 次,GitHub 1 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

jj-vcs 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 3 个目录同时收录,说明这个 Skill 流传比较广。
  • 许可证明确为 MIT,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 需要执行命令,装到常用环境前要先评估影响面。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理运维和基础设施类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 不能接受 Skill 在你机器上执行命令的人。
  • 需要厂商级技术支持和 SLA 的生产系统。

运维和基础设施类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
brainstorming

头脑风暴 · Codex、Claude

3,148,776173,131操作浏览器MIT通过
copywriting

文案写作 · Codex、Claude

1,996,72425,583需要联网MIT通过
openclaw-secure-linux-cloud

OpenClaw secure linux cloud 命令行 · Codex、Claude

1,853,08840接触敏感数据未明确未通过
xget

xget 命令行 · Codex、Claude

1,799,28040执行命令未明确未通过
requesting-code-review

代码审查请求 · Codex、Claude

1,590,144173,103权限未标注MIT通过
jj-vcs

杰杰 VCS · 本页

8651执行命令MIT通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Jujutsu (jj) Version Control System

Jujutsu is a next-generation version control system that uses Git repositories as storage while providing a fundamentally different and more powerful user experience. This skill includes the complete official documentation from the jj repository.

Quick Start: Read tutorial.md for hands-on introduction. See git-comparison.md for Git users migrating to jj.

What is Jujutsu?

Jujutsu (command: jj) is a VCS designed to be easy to use for both beginners and experienced users. Key innovations include:

  • Working-copy-as-a-commit: Changes are automatically recorded as commits and amended on each change
  • Operation log & undo: Every operation is recorded and can be undone (like version control for your version control!)
  • Automatic rebase: When you modify a commit, descendants are automatically rebased
  • First-class conflicts: Conflicts are tracked as objects and can be committed, resolved later, and propagated
  • No staging area: Simplified workflow without Git's index/staging complexity
  • Git compatible: Works with existing Git repositories and forges like GitHub

Documentation Structure

Getting Started

  • README.md - Project overview, key features, and introduction
  • index.md - Documentation homepage with useful links
  • install-and-setup.md - Installation instructions for all platforms and initial configuration
  • tutorial.md - Comprehensive hands-on tutorial (assumes Git knowledge)
  • FAQ.md - Frequently asked questions and common issues
  • glossary.md - Definitions of jj-specific terminology

Core Concepts

  • working-copy.md - How the working copy works as a commit
  • operation-log.md - Understanding the operation log and undo functionality
  • conflicts.md - How jj handles merge conflicts as first-class objects
  • revsets.md - Powerful language for selecting revisions (like Mercurial revsets)
  • templates.md - Customizing output formatting with the template language
  • bookmarks.md - Working with bookmarks (similar to Git branches)
  • filesets.md - Language for selecting files

Configuration

  • config.md - Complete configuration reference and options
  • config.toml - Example configuration file
  • cli-reference.md - Command-line interface reference

Git Integration

  • git-compatibility.md - How jj works with Git repositories and Git features
  • git-comparison.md - Comparison of jj vs Git workflows and commands
  • git-command-table.md - Quick reference table mapping Git commands to jj equivalents
  • github.md - Working with GitHub repositories and pull requests
  • gerrit.md - Working with Gerrit code review system

Guides

  • guides/divergence.md - Understanding and resolving divergent changes
  • guides/multiple-remotes.md - Working with multiple remote repositories

Technical Documentation

  • technical/architecture.md - High-level architecture and design decisions
  • technical/concurrency.md - How jj handles concurrent operations safely
  • technical/conflicts.md - Technical details of conflict handling

Development and Contributing

  • contributing.md - How to contribute to jj development
  • code-of-conduct.md - Community code of conduct
  • core_tenets.md - Core principles guiding jj's design
  • roadmap.md - Development roadmap and planned features
  • community_tools.md - Community-maintained tools and integrations
  • releasing.md - Release process documentation
  • design_docs.md - Index of design documents
  • design_doc_blueprint.md - Template for writing design docs

Comparisons and Context

  • sapling-comparison.md - Comparison with Meta's Sapling VCS
  • related-work.md - Other related version control systems
  • testimonials.md - User testimonials and experiences

Platform-Specific

  • windows.md - Windows-specific considerations and setup

Project Information

  • CHANGELOG.md - Version history and release notes
  • GOVERNANCE.md - Project governance structure
  • SECURITY.md - Security policy and reporting

Common Usage Patterns

When the user asks to:

  • Get started with jj → Check tutorial.md and install-and-setup.md
  • Migrate from Git → Check git-comparison.md and git-command-table.md
  • Understand a concept → Check glossary.md and relevant concept docs (working-copy, conflicts, etc.)
  • Configure jj → Check config.md
  • Work with GitHub → Check github.md
  • Select revisions → Check revsets.md
  • Customize output → Check templates.md
  • Handle conflicts → Check conflicts.md
  • Troubleshoot issues → Check FAQ.md
  • Undo a mistake → Check operation-log.md
  • Understand architecture → Check technical/architecture.md

Quick Command Reference

Basic Operations

# Clone a Git repository
jj git clone <url>

# Check status
jj st  # or jj status

# Create a new change
jj new

# Edit a change description
jj describe

# Show change log
jj log

# Undo last operation
jj undo

# Show operation log
jj op log

Working with Changes

# Abandon a change
jj abandon

# Move changes between commits
jj squash  # move changes into parent
jj move    # move changes to another commit

# Rebase changes
jj rebase -r <revision> -d <destination>

# Resolve conflicts
jj resolve  # interactive conflict resolution

Git Integration

# Fetch from Git remote
jj git fetch

# Push to Git remote
jj git push

# Import Git branches as bookmarks
jj bookmark track <name>@<remote>

Selecting Revisions (Revsets)

# Common revset expressions
@              # working copy commit
@-             # parent of working copy
main@origin    # bookmark from remote
::@            # ancestors of working copy
@::            # descendants of working copy
~empty()       # non-empty changes

Key Concepts to Understand

Working Copy as Commit

  • The working copy is always a commit (shown as @)
  • Changes are automatically committed as you work
  • No explicit commit command needed (use jj describe to add a message)
  • Use jj new to start a new change

Revsets

  • Powerful language for selecting commits (similar to Mercurial)
  • Used in many commands: jj log -r, jj show, jj rebase, etc.
  • Supports boolean operations, functions, and composition
  • See revsets.md for complete reference

Operation Log

  • Every jj operation is recorded (commit, rebase, push, etc.)
  • Use jj op log to see operation history
  • Use jj undo to undo the last operation
  • Use jj op restore to restore to any previous state

Bookmarks vs Branches

  • jj uses "bookmarks" which are similar to Git branches but simpler
  • Changes can exist without bookmarks (anonymous branches)
  • Bookmarks are just pointers, not required for workflow
  • Git branches are imported as bookmarks

Conflicts

  • Conflicts are stored in commits, not just in working copy
  • You can commit conflicted changes and resolve later
  • Conflict resolution is propagated through rebases
  • Use jj resolve for interactive resolution

File Organization

  • README.md - Main project README with overview
  • docs/ - All documentation files

- tutorial.md - Getting started tutorial - config.md - Configuration reference - revsets.md - Revset language reference - templates.md - Template language reference - **git-*.md - Git integration documentation - guides/ - How-to guides for specific workflows - technical/ - Technical architecture documentation - design/** - Design documents for features

Tips

  • Start with the tutorial to understand the jj mental model
  • Use jj help <command> for detailed command help
  • The operation log is your safety net - don't be afraid to experiment
  • Revsets are powerful - learn them to work efficiently
  • Conflicts are normal and can be handled gracefully
  • jj works best when you embrace its philosophy (working-copy-as-commit, auto-rebase)
  • Check the FAQ when you encounter unexpected behavior
  • Use templates to customize jj log output to your preferences

Important Notes

  • Jujutsu is experimental but actively developed and used daily by its developers
  • Git compatibility is stable - safe to use with existing Git workflows
  • Some features are experimental (check README warnings)
  • Breaking changes may occur but are documented in CHANGELOG
  • Community is active on Discord, GitHub Discussions, and IRC (#jujutsu on Libera Chat)

Resources

平台分布

Claude Code

28.63%
按下载量换算78

OpenCode

21.93%
按下载量换算60

Gemini CLI

15.79%
按下载量换算43

Antigravity

11.72%
按下载量换算32

Codex

7.17%
按下载量换算20

kilo

3.35%
按下载量换算9

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

执行命令

安装流程涉及命令执行,可能通过 npx skills add https://github.com/seckatie/katies-ai-skills --skill jj-vcs;npx skills add seckatie/katies-ai-skills --skill "jj-vcs" 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。

继续浏览同类 Skills