do-git

Executes lifecycle-aware git intents with previewed, confirmed command sequences and safety gates.

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/khoavu882/do-flow --skill do-git-khoavu882
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: do-git
Source: https://github.com/khoavu882/do-flow/tree/main/core/shared/skills/do-git
Command: npx skills add https://github.com/khoavu882/do-flow --skill do-git-khoavu882

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Running git operations by hand risks destructive mistakes like force-pushes, history rewrites, or unpropagated hotfixes, and ad-hoc commands skip the confirmation and policy checks teams need. This Skill wraps git work in named lifecycle intents that preview every command, fingerprint repository state, and require explicit confirmation before mutating anything. ## Core Features & Use Cases - Lifecycle Intents: Run start, save, sync, ship, release, hotfix, backport, and status intents that derive branch names and versions from repository policy rather than guesswork. - Preview-and-Confirm Safety: Every mutating intent composes a concrete command sequence, fingerprints the working tree, and aborts if state changes before execution. - Release and Hotfix Rituals: Automate version manifest updates, CHANGELOG drafting, annotated tagging, and hotfix propagation across production, integration, and release branches with halt-on-conflict reporting. - Use Case: A developer finishes a feature and runs the ship intent; the Skill previews the exact merge commands against the integration branch, waits for confirmation, executes, and reports each step's result. ## Quick Start Ask the assistant to commit your current changes with an intelligent message using the do-git save intent, then review and confirm the previewed commands.

Frequently Asked Questions about do-git

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

FAQPage Schema
How do I safely commit and ship a feature branch with git?▼

Use the save intent to stage and commit changes with a message generated from the actual diff, then the ship intent to merge into the integration branch. Both intents preview the exact commands and require your confirmation before executing.

How do I create and propagate a git hotfix across branches?▼

Invoke the hotfix intent with a fix reference; it branches from production, tags a patch version, merges to production, then propagates to integration and active release branches. On a conflicting cherry-pick it halts and reports all outstanding targets.

Can I still run raw git commands like status or log?▼

Yes, any unrecognized first token falls through to raw git passthrough, so commands like log, diff, or status work unchanged. Destructive raw operations still trigger state checks and confirmation gates.

Does this skill create pull requests or manage CI pipelines?▼

No, forge API calls such as pull request creation and pipeline watching are explicitly out of scope, as are CI/CD setup and branch protection scaffolding. It handles local and remote git operations only.

What happens if the repository state changes before execution?▼

The skill fingerprints the working tree at preview time and re-fingerprints before executing. If the fingerprint changed, it aborts and re-previews rather than running a stale command sequence.