git-workflow

Orchestrate Git workflows with atomic commits and ephemeral branches.

4|3|Updated Feb 25, 2026

Search Tags:#branching #task-management #code-review #atomic-commits #git-workflow #pull-request #ai-assisted

Ready to run

npx skills add https://github.com/Open-Paws/no-animal-violence --skill git-workflow-open-paws

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/Open-Paws/no-animal-violence/tree/main/.claude/skills/git-workflow
Command: npx skills add https://github.com/Open-Paws/no-animal-violence --skill git-workflow-open-paws

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured Git workflow that prevents runaway changes by forcing atomic commits, ephemeral branches, and curated PRs for AI-assisted advocacy projects.

Core Features & Use Cases

Atomic commits per subtask to keep history clean and reviewable.
Ephemeral branching strategy to minimize long-lived branches and merge conflicts.
PR curation guidelines to create small, reviewable batches of changes.
AI-assisted tagging and attribution to track agent-generated work.

Quick Start

Create an ephemeral branch for the current task, split work into atomic commits for each subtask, and curate small reviewable PRs.

Frequently Asked Questions about git-workflow

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

FAQPage Schema

How do I manage AI-assisted git workflows with atomic commits?▼

To manage AI-assisted git workflows with atomic commits, create ephemeral branches for tasks and break work into small, reviewable commits. This enforces per-subtask commits, requires test verification before committing, and ensures clean, reviewable project history.

What is the best way to structure pull requests for AI-generated code?▼

The best way to structure pull requests for AI-generated code is through staged PR curation, creating small batches of changes for review. This approach enforces accountability tagging to properly track and attribute agent-generated work within the repository.

Why use ephemeral branches for task-based coding sessions?▼

You should use ephemeral branches for task-based coding sessions to minimize long-lived branches and reduce merge conflicts. This branching strategy keeps changes isolated, forces atomic commits per subtask, and maintains a clean, reviewable project history.

Does this git workflow require test verification before committing?▼

Yes, this git workflow enforces test verification before committing changes. It orchestrates a disciplined process requiring tests to pass for each subtask, ensuring atomic commits remain stable and preventing runaway changes in AI-assisted development.

How do I attribute AI-generated content in git commit messages?▼

You attribute AI-generated content in git commit messages by applying accountability tagging during the workflow. This tracks agent-generated work alongside clear commit messages and staged PR curation to properly document AI-assisted advocacy development.