ck:git

Guide Git staging, conventional commits, pushes, PRs, and merges with secret scanning.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/MinhHoangDono/antigravity-kit --skill ck-git-minhhoangdono
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:git
Source: https://github.com/MinhHoangDono/antigravity-kit/tree/main/.agent/skills/git
Command: npx skills add https://github.com/MinhHoangDono/antigravity-kit --skill ck-git-minhhoangdono

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines common Git operations by guiding you through staging, conventional-commit message formatting, optional pushing, and PR/merge actions while adding a lightweight secrets scan to reduce accidental credential commits.

Core Features & Use Cases

  • Guided git operations: Supports cm (commit), cp (commit + push), pr (create PR), and merge (merge branches).
  • Conventional-commit workflow with auto-splitting: Decides whether to split into multiple commits based on mixed types/scopes, file groups, and size thresholds.
  • Pre-commit secret scanning: Scans staged diffs for common secret patterns and blocks the commit if matches are found.
  • Remote-first PR safety: Uses remote branch diffs and sync steps to avoid relying on local/unpushed comparisons.

Quick Start

Run the Git commit flow by asking for: "ck:git cm".

Frequently Asked Questions about ck:git

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

FAQPage Schema
How do I split a git commit with mixed types and scopes automatically?

Splitting a git commit for mixed types and scopes is handled automatically based on file groups and size thresholds. This conventional-commit workflow evaluates staged diffs and enforces splitting rules to maintain a structured commit history without manual intervention.

Can I scan staged diffs for secrets before pushing a git commit?

Scanning staged diffs for secrets before pushing a git commit is fully supported. The workflow performs a pre-commit secret scan targeting common credential patterns and blocks the commit process entirely if any risky matches are found.

What is the best way to create a pull request using remote branch diffs?

Creating a pull request using remote branch diffs ensures accuracy by syncing with the remote repository first. This remote-first PR safety mechanism avoids relying on local or unpushed comparisons, generating a PR based on true remote state.

How does conventional commit formatting work for feature work and release integration?

Conventional commit formatting for feature work and release integration works by guiding the staging and message formatting process. It automatically determines commit type and scope, splitting commits when necessary to ensure a clean, structured history for collaborative PR workflows.

Do I need a specific git workflow to merge branches safely?

A specific git workflow is not required to merge branches safely, but structured guardrails are enforced. The merge process is executed via a dedicated subagent, ensuring clearer outputs and preventing risky changes from being integrated during release integration.