git

Automates Git workflows with non-interactive commands and conventional commits for auditable linear history.

Updated Jan 2, 2026
One-click install
npx skills add https://github.com/Cogni-AI-OU/xero-fin-ops --skill git-cogni-ai-ou
Or copy as Structured Prompt for Agentā–¼
Please help me install this Agent Skill.
Skill: git
Source: https://github.com/Cogni-AI-OU/xero-fin-ops/tree/main/.github/skills/git
Command: npx skills add https://github.com/Cogni-AI-OU/xero-fin-ops --skill git-cogni-ai-ou

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides repository agents to perform Git operations safely, non-interactively, and with auditable history, reducing human error and preserving project conventions.

Core Features & Use Cases

  • Non-interactive execution: Commands run without prompts to support automation.
  • Linear history: Favor rebases and squashes to keep history clean and bisectable.
  • Atomic commits and conventional commits: Encourage small, well-described commits with standard prefixes.
  • Hook-aware workflows: Respect pre-commit and pre-push hooks, with safe fallback paths.
  • Safe conflict resolution: Provide deterministic strategies to resolve conflicts non-destructively in automation scenarios.

Quick Start

Run non-interactive git commands that maintain a clean, auditable history on your feature branch.

Frequently Asked Questions about git

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

FAQPage Schema
How do I run non-interactive Git workflows in CI/CD pipelines without prompts blocking automation?ā–¼

Non-interactive Git workflows execute commands without prompts to support CI/CD pipelines and automation bots. Commands run automatically, applying deterministic strategies to maintain auditable, linearly structured history without requiring manual input.

What is the best way to resolve Git conflicts non-destructively in automation scenarios?ā–¼

Safe conflict resolution in automation scenarios uses deterministic strategies to resolve conflicts non-destructively. This approach applies robust error handling and predefined rules to automate conflict resolution during non-interactive Git workflows.

How do I maintain a linear Git history using rebasing and squashing for bulk maintenance tasks?ā–¼

Linear history is maintained by favoring rebases and squashes to keep history clean and bisectable. This approach supports bulk maintenance tasks by ensuring an auditable, linearly structured history across repository automation.

Can I use conventional commits with hook-aware Git operations in repository automation?ā–¼

Conventional commits are supported alongside hook-aware Git operations. Atomic commits use standard prefixes while respecting pre-commit and pre-push hooks, providing safe fallback paths during non-interactive repository automation.

Does non-interactive Git automation work with pre-commit and pre-push hooks?ā–¼

Non-interactive Git automation is hook-aware and respects both pre-commit and pre-push hooks. It provides safe fallback paths to ensure workflows continue without manual intervention while preserving project conventions.

Why does non-interactive rebasing fail when hooks prompt for input during automated workflows?ā–¼

Non-interactive rebasing can fail when hooks trigger prompts that block automation. This Skill addresses the limitation by providing hook-aware workflows with safe fallback paths, ensuring robust error handling and deterministic conflict resolution.