setup-git

Name: setup-git
Availability: InStock
Author: PacificStudio

Install Git, set user identity from ticket context, and verify basic workflow.

264|27|Updated Mar 19, 2026

Search Tags:#automation #git #devops #authentication #setup #identity #agent-work

Ready to run

npx skills add https://github.com/PacificStudio/openase --skill setup-git

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: setup-git
Source: https://github.com/PacificStudio/openase/tree/main/internal/builtin/skills/setup-git
Command: npx skills add https://github.com/PacificStudio/openase --skill setup-git

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates installing Git on a target machine and ensures the minimum identity configuration needed for reliable agent work.

Core Features & Use Cases

Ensure Git is installed; verify that git --version works and install if missing.
Validate and set git user.name and git user.email from the ticket context when they are not configured.
Repair Git authentication only when there is a real credential problem, avoiding overwriting a working setup.
Finish with non-destructive checks that confirm a basic Git workflow (commit, push) works and record the effective configuration.

Quick Start

Install Git on the target machine if missing, then set git user.name and git user.email from the ticket context and verify basic Git functionality.

Frequently Asked Questions about setup-git

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

FAQPage Schema

How do I install Git and set up user identity for automated agent workflows?▼

Git setup for agent workflows involves verifying the Git version, installing it if missing, and configuring user.name and user.email from the ticket context to ensure reliable non-destructive commit and push operations.

What's the best way to fix Git authentication without breaking a working setup?▼

Fixing Git authentication should be conditional, triggering repair only when a real credential problem exists. This non-destructive approach avoids overwriting existing working setups while verifying basic commit and push functionality.

Why does my Git user identity need to match ticket context for agent work?▼

Git user identity must match ticket context because agent-driven workflows require accurate user.name and user.email configuration for traceability. Setting identity from ticket context ensures commits are properly attributed during automated deployments.

How do I verify Git is installed and configured correctly on a new machine?▼

Verify Git installation by running git --version, then confirm user.name and user.email are set. Finish with non-destructive checks that test basic commit and push workflows and record the effective configuration.

When should I not use automated Git identity setup?▼

Avoid automated Git identity setup when a working configuration already exists. The process is designed to apply identity only when settings are not configured and to repair authentication solely when real credential problems are detected.

Does Git setup automation support ticket-driven deployment workflows?▼

Git setup automation directly supports ticket-driven deployment workflows by extracting user identity from ticket context, provisioning Git on target machines, and validating that basic commit and push operations function correctly.