local-workspace-git-bootstrap

Initialize a top-level Git repository excluding secrets, caches, and nested repos.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/quiznat/Hermes_Sapho --skill local-workspace-git-bootstrap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: local-workspace-git-bootstrap
Source: https://github.com/quiznat/Hermes_Sapho/tree/main/.hermes/skills/software-development/local-workspace-git-bootstrap
Command: npx skills add https://github.com/quiznat/Hermes_Sapho --skill local-workspace-git-bootstrap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Initialize a new top-level Git repo for an existing local workspace while excluding secrets, runtime state, caches, and nested upstream repositories; also add a backup script to capture ignored state for safe off-machine storage.

Core Features & Use Cases

  • Defensive initialization: creates a clean, top-level repository with a safety-first .gitignore.
  • Secrets and state exclusion: automatically excludes sensitive files and volatile runtime data.
  • Nested repo handling: detects nested Git repositories and avoids embedding them.
  • Backup path: provides a script to snapshot ignored-state data for later backups.
  • Documentation: includes guidance on remote setup and maintenance.

Quick Start

Run this skill on your local workspace to initialize a safe top-level Git repository that excludes secrets and runtime state while adding a backup script for ignored data.

Frequently Asked Questions about local-workspace-git-bootstrap

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

FAQPage Schema
How do I initialize a git repository in a local workspace without committing secrets and caches?

To initialize a git repository safely, this Skill bootstraps a top-level workspace repo with a defensive .gitignore that automatically excludes secrets, runtime state, caches, and volatile data.

What happens to nested git repositories when I bootstrap a top-level workspace repo?

When bootstrapping a top-level workspace repo, the Skill detects nested upstream git repositories and excludes them from version control to prevent embedding them directly in the parent history.

Can I backup the ignored files and runtime state that are excluded from my workspace git repo?

Yes, you can backup ignored files because the Skill adds a dedicated backup script that snapshots all ignored-state data, allowing you to securely store volatile runtime state and secrets off-machine.

What's the best way to add version control to an existing project directory containing sensitive configuration files?

The best way to add version control to a directory with sensitive files is using a safety-first initialization process that identifies and excludes sensitive paths while establishing a clean git history.

Why do I need a defensive .gitignore when setting up version control for my local workspace?

You need a defensive .gitignore to prevent accidentally tracking sensitive paths, runtime caches, and nested repos, ensuring that only your intended workspace files are committed to git history.