Fossil SCM Usage

Document Fossil SCM CLI workflows for repository setup, commits, branching, merging, diffing, and ticketing.

4|1|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/egravert/egravert-marketplace --skill fossil-scm-usage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Fossil SCM Usage
Source: https://github.com/egravert/egravert-marketplace/tree/main/fossil-scm/skills/fossil-usage
Command: npx skills add https://github.com/egravert/egravert-marketplace --skill fossil-scm-usage

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Learning and applying Fossil SCM CLI workflows for repository setup, daily operations, and ticket management can be challenging without a cohesive reference.

Core Features & Use Cases

  • Comprehensive Fossil CLI guidance covering init, clone, open, add, commit, update, branch, merge, timeline, and ticket commands.
  • Scenario-based workflows and quick-start examples for common development tasks in single-repo workflows.
  • Use case: A developer initializes a repo, opens a working checkout, makes commits, creates a feature branch, and resolves tickets in a coordinated sequence.

Quick Start

Guide me through setting up a Fossil repository, opening a working checkout, and performing common workflows like commit, branch, and merge.

Frequently Asked Questions about Fossil SCM Usage

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

FAQPage Schema
How do I set up a Fossil SCM repository and open a working checkout?

To set up a Fossil SCM repository, initialize it using the CLI, then open a working checkout directory. This process creates the local repository file and populates your workspace with the current source tree.

What is the best way to manage branching and merging in Fossil?

Managing branching and merging in Fossil involves creating feature branches from the timeline and integrating them back via merge commands. This approach coordinates development sequences and maintains a structured project history.

Can I handle ticketing and issue tracking directly within Fossil SCM?

Yes, Fossil SCM includes built-in ticketing capabilities. You can resolve tickets and track issues directly through the CLI, coordinating sequences with commits and branches in a single-repo workflow.

How do I clone a Fossil repository and review the project timeline?

Cloning a Fossil repository copies the remote database locally, allowing you to open a workspace and review the project timeline. The timeline command provides a chronological view of commits and branches.

Does Fossil SCM support common version-control workflows like diff and update?

Yes, Fossil SCM supports common version-control workflows including diff and update. These CLI commands allow you to inspect file changes and synchronize your working checkout with specific repository versions.