ck:git

Automate Git staging, commits, pushes, PRs, and merges with conventional commits.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Git teams waste time on manual setup, inconsistent commits, and risky pushes.

Core Features & Use Cases

  • Staging, committing, pushing, PR creation, and merging with conventional commits.
  • Auto-splits commits by type and scope to improve code review and history clarity.
  • Security checks to detect secrets before committing and pushing.

Quick Start

Align your local workflow with conventional commits and run the guided steps to stage, commit, and push changes.

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 commits and pushes with conventional commit formats?

You can automate git commits and pushes by using a structured workflow that enforces conventional commits, auto-stages changes, and splits commits by type and scope for a consistent history.

What is the best way to split git commits by type and scope automatically?

Splitting git commits by type and scope is handled by an automated workflow that categorizes staged changes, ensuring clearer code review and a structured, conventional commit history.

How do I run secret security scans before pushing git changes?

Running secret security scans before pushing involves executing in-workflow security checks that detect sensitive data during the staging and committing phases to prevent risky pushes.

Can I automate pull request creation and merging within a conventional commit workflow?

Yes, you can automate pull request creation and merging by applying a guided git workflow that integrates conventional commits directly into the PR generation and merge operations.

Do I need any specific environment setup to enforce conventional commits in my git workflow?

Enforcing conventional commits requires activating a context-engineering environment and utilizing a git-manager subagent to streamline the staging, committing, and pushing operations.

Why should software teams use automated conventional commits instead of manual git operations?

Automated conventional commits eliminate manual setup friction and inconsistent history by enforcing structured staging, auto-splitting commits, and running security scans before risky pushes occur.