cvs

Coordinate local version control and remote platform operations from environment settings.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/dragoscirjan/opencode-config --skill cvs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cvs
Source: https://github.com/dragoscirjan/opencode-config/tree/main/skills/cvs
Command: npx skills add https://github.com/dragoscirjan/opencode-config --skill cvs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes guesswork from working with local version control and remote repository platforms by enforcing the correct tools and rules for each environment.

Core Features & Use Cases

  • Tool Selection by Environment: Reads CVS_TOOL to determine which local VCS client and which remote platform tools must be used.
  • Cross-Platform Repository Operations: Supports GitHub, GitLab, and Forgejo workflows for branches, commits, pushes, issues, pull requests, and comments.
  • Issue Tracking Discipline: Applies the issue-tracking mode and explicitly prevents label usage so repository workflows stay consistent.
  • Use Case: When a project uses git locally and GitHub remotely, this Skill ensures the assistant uses git for local changes and the correct GitHub tools for remote actions.

Quick Start

Ask the assistant to follow the CVS mode rules, read CVS_TOOL, and carry out your repository task using the required local and remote tools.

Frequently Asked Questions about cvs

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

FAQPage Schema
How do I coordinate git local commits with GitHub remote repository operations?

By reading the CVS_TOOL environment setting, it ensures git is used for local commits while the correct GitHub remote tools handle pushes, pull requests, and comments.

Can I use this version-control workflow with GitLab and Forgejo repositories?

Yes, this version-control workflow supports GitLab and Forgejo repositories alongside GitHub. It applies platform-specific remote actions for branches, issues, and pull requests across all three environments.

What is the best way to manage issue tracking across multiple remote platforms?

The best way to manage issue tracking across platforms is through the ISSUE_TRACKING environment setting, which enforces a no-label issue policy to keep repository workflows consistent across GitHub, GitLab, and Forgejo.

Does this version-control Skill prevent label usage when creating issues?

Yes, this version-control Skill explicitly prevents label usage during issue creation. It applies the issue-tracking mode and enforces a strict no-label issue policy to maintain consistent repository workflows.

How do I configure version-control tools for different repository environments?

You configure version-control tools by setting the CVS_TOOL and ISSUE_TRACKING environment variables. The Skill reads these settings to determine which local VCS client and remote platform tools must be used for your repository tasks.