speckit-git-initialize

Initialize a Git repository with an initial commit in a project directory.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/tellbom/process --skill speckit-git-initialize-tellbom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-initialize
Source: https://github.com/tellbom/process/tree/main/.agents/skills/speckit-git-initialize
Command: npx skills add https://github.com/tellbom/process --skill speckit-git-initialize-tellbom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Initialize a Git repository in a project that has no version control to establish a baseline history with an initial commit.

Core Features & Use Cases

  • Initialize a new Git repository in the current directory if none exists.
  • Stage all files and commit with a standard initial message.
  • Gracefully handle environments without Git or when already inside a repository, continuing work without blocking workflows.
  • Optional customization via project-provided scripts for ignore templates, default branch naming, and hooks.

Quick Start

Initialize a Git repository in the current project directory if one does not already exist.

Frequently Asked Questions about speckit-git-initialize

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

FAQPage Schema
How do I initialize a Git repository with an initial commit in a project directory?

To initialize a Git repository, the Skill automates staging all files and creating an initial commit in your project directory, establishing a consistent baseline history even without a Git CLI.

What happens if I try to initialize a Git repo in an environment without Git installed?

Without Git installed, the Skill gracefully handles the environment by continuing work without blocking workflows, ensuring your project setup proceeds even when the Git CLI is missing.

Can I customize the initial commit message and branch naming for my version control setup?

Yes, you can customize version control setup via optional project-provided override scripts in the project root, allowing template-driven customization for ignore templates, default branch naming, and hooks.

Does initializing a Git repository work if the project is already inside an existing repository?

If already inside an existing repository, the Skill gracefully handles the situation by continuing work without blocking workflows, ensuring it does not disrupt your current version control history.

What is the best way to establish a baseline version control history for a new project?

The best way to establish baseline version control is using this Skill to initialize the repository, stage all files, and commit with a standard initial message for consistent project history.