own-your-history

Automate Git installation and version history setup for Founder OS.

2|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/ARCASSystems/FounderOS --skill own-your-history
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: own-your-history
Source: https://github.com/ARCASSystems/FounderOS/tree/main/skills/own-your-history
Command: npx skills add https://github.com/ARCASSystems/FounderOS --skill own-your-history

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the installation of Git and sets up full version history for a Founder OS install, ensuring that all changes are tracked and versioned.

Core Features & Use Cases

  • Automated Git Installation: Installs Git automatically without manual intervention.
  • Version History Setup: Converts the folder into a repository and records the first version.
  • Privacy Guard: Wires the privacy guard to protect private names from being committed.
  • Consent-Gated: The process is only initiated after explicit consent from the user.
  • Use Case: A user with a Founder OS install that does not have version history can trigger this Skill to set up Git and enable full versioning.

Quick Start

Run the command 'own my history' to start the process of setting up full version history.

Frequently Asked Questions about own-your-history

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

FAQPage Schema
How do I set up Git version control for a Founder OS installation?

Git version control for Founder OS is set up by an automated Skill that installs Git, converts your folder into a repository, and records the first version after you provide explicit consent.

Can I enable full version history without manually installing version control software?

You can enable full version history without manual installation by running the 'own my history' command, which automates Git setup and initiates version tracking for your directory.

Does version control setup protect private names from being committed to the repository?

The version control setup protects private names from being committed by wiring a privacy guard into your repository, ensuring sensitive information is excluded from the tracked version history.

Do I need to configure my Git user identity to track version history?

You need to configure your Git user identity locally to track version history, as the setup requires local execution and user identity configuration to properly attribute recorded changes.

What is the best way to convert an existing folder into a versioned repository?

Converting an existing folder into a versioned repository is best handled by an automated setup tool that initializes Git, configures your identity, and records the initial version.