ck:git

Automate Git staging, committing, pushing, PR creation, and merges with security checks.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/EdgeHunt/EdgeHunt --skill ck-git-edgehunt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:git
Source: https://github.com/EdgeHunt/EdgeHunt/tree/main/.claude/skills/git
Command: npx skills add https://github.com/EdgeHunt/EdgeHunt --skill ck-git-edgehunt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Teams often struggle with inconsistent commits, manual PR processes, and risky merges that slow development and introduce errors. This Skill standardizes Git operations, automates staging, committing, pushing, and PR workflows, and adds security checks to prevent leaking secrets.

Core Features & Use Cases

  • Enforce conventional commits and structured messages for better traceability.
  • Automate staging, committing, pushing, PR creation, and merging to reduce manual toil.
  • Perform pre-commit security scans to detect secrets and credentials.
  • Split large changes into meaningful commits by type and scope, improving review quality.
  • Use the git-manager subagent to isolate verbose output and maintain clean logs.

Quick Start

Choose a git operation code (cm, cp, pr, or merge) and the skill will guide you through staging, committing, pushing, PR creation, or merging with safety checks.

Frequently Asked Questions about ck:git

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

FAQPage Schema
How do I automate git workflows with conventional commits?

Automating git workflows with conventional commits involves standardizing staging, committing, and pushing operations. This Skill uses a git-manager subagent to isolate verbose output and enforce structured commit messages for better traceability.

Can I automatically split large changes into meaningful commits by type and scope?

Yes, you can split large changes into meaningful commits by type and scope. This improves review quality by ensuring structured messages and conventional commits are maintained across team environments.

How do I run pre-commit security scans to detect secrets and credentials?

Pre-commit security scans detect secrets and credentials by validating safety during git operations. The Skill performs these checks automatically before staging and committing to prevent leaking secrets into the repository.

What is the best way to automate pull request creation and merging?

Automating pull request creation and merging is best handled by selecting a specific git operation code. The Skill guides you through PR creation and merging while validating safety and error handling during the operation.

Does this git automation tool work for team environments?

Yes, this git automation tool works for team environments. It standardizes git operations, enforces conventional commits, and performs security checks to ensure consistent workflows across multiple team members.

Why should I use conventional commits in my git workflow?

Using conventional commits in your git workflow provides better traceability and structured messages. It reduces manual toil by automating staging, committing, and PR creation while preventing risky merges and inconsistent commits.