git

Perform granular git stage, commit, push, PR, and merge workflows with safety checks.

5|Updated May 2, 2026
One-click install
npx skills add https://github.com/vanducng/skills --skill git-vanducng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git
Source: https://github.com/vanducng/skills/tree/main/skills/git
Command: npx skills add https://github.com/vanducng/skills --skill git-vanducng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Low-level git toolkit for the moments when you don't want the full vd:ship pipeline — just a clean commit, a quick push, a PR, or a merge. Keeps verbose git output out of main context by delegating to the git-manager subagent.

Core Features & Use Cases

  • Checkpoint commits: stage, analyze, and split commits when appropriate to keep history clean.
  • Selective ops: perform cm, cp, pr, and merge operations without invoking the full ship pipeline.
  • Safety first: hard safety rules block on secrets and enforce conventional-commit formats; remote-first diffs minimize drift.
  • Auditable flow: outputs are structured and delegated to a subagent for consistent results.

Quick Start

Use the vd:git cm command to stage, analyze, and commit changes.

Frequently Asked Questions about git

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

FAQPage Schema
How do I make clean git commits without running a full deployment pipeline?

You can perform selective git operations like stage, commit, and push without invoking a full ship pipeline. Granular git ops enforce conventional-commit formats and delegate verbose output to a subagent, keeping your main context clean.

Can I create a pull request and merge branches without triggering the entire ship workflow?

Yes, selective git operations support pull request and merge workflows independently. These operations include safety checks like secret scanning and origin-based diffs to ensure safe, auditable merges without the full ship pipeline.

How does secret scanning work during git commit and push operations?

Hard safety rules block git operations when secrets are detected during commit and push workflows. This prevents accidental credential exposure by scanning staged changes before any granular operation proceeds.

What's the best way to split checkpoint commits to keep git history clean?

Granular git operations analyze staged changes and split commits when appropriate to maintain clean history. This approach enforces conventional-commit formats and ensures each checkpoint remains focused and auditable.

Does this git workflow enforce conventional commit formats automatically?

Yes, hard safety rules enforce conventional-commit formats automatically during stage and commit operations. This ensures consistent message structure across all checkpoint commits without manual formatting checks.

Why should I use granular git ops instead of a full ship pipeline for quick pushes?

Granular git ops let you perform quick pushes without the overhead of a full ship pipeline. They delegate verbose output to a subagent and apply safety checks, ensuring fast, clean, and auditable operations.