ck:git

Automate git staging, committing, pushing, and pull request creation.

Updated May 10, 2026
One-click install
npx skills add https://github.com/dthuy62/kollet-app --skill ck-git-dthuy62
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:git
Source: https://github.com/dthuy62/kollet-app/tree/main/.opencode/skills/git
Command: npx skills add https://github.com/dthuy62/kollet-app --skill ck-git-dthuy62

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It removes the risk and overhead of performing git operations manually, especially when staging, committing, pushing, opening pull requests, or merging branches in a consistent and safe way.

Core Features & Use Cases

  • Conventional commit creation with automatic split decisions for mixed changes.
  • Secure workflows that scan staged diffs for secrets before committing.
  • Pull request and merge guidance using remote-aware branch analysis and GitHub CLI support.
  • Use case: a developer edits code, docs, and config across several files and wants the skill to stage, separate, and commit each change set correctly while protecting credentials.

Quick Start

Ask this skill to stage your changes, scan for secrets, and create the appropriate conventional commit or pull request workflow for the current branch.

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 with conventional commit formatting?

Automating conventional commit formatting requires analyzing staged diffs, splitting mixed edits, and enforcing secret scanning before pushing. This keeps repository workflows deterministic and secure while removing manual staging overhead from your daily development cycle.

How do I split mixed staged changes into separate git commits?

Splitting mixed staged changes into separate git commits requires analyzing the staged diff to identify distinct change sets, such as separating code edits from documentation updates. This allows each logical change set to be committed independently with proper conventional commit messages.

Can I automate pull request creation and branch merging using GitHub CLI?

Automating pull request creation and branch merging with GitHub CLI involves comparing remote branches, performing branch safety checks, and managing feature branches. This remote-aware analysis ensures secure merges and consistent pull request workflows directly from your local environment.

How do I scan staged git diffs for secrets before pushing to a remote repository?

Scanning staged git diffs for secrets before pushing requires a security check that analyzes your pending changes for exposed credentials. This preventative step blocks sensitive data from entering the commit history and ensures remote repository safety.

What is the best way to manage feature branches and compare remote branches safely?

Managing feature branches and comparing remote branches safely requires remote-first diff analysis and branch safety checks before executing merges. This approach prevents conflicting deployments and maintains a clean, deterministic history across your repository's active development lines.

Do I need the GitHub CLI installed to automate pull request workflows and branch merges?

GitHub CLI is required to automate pull request creation and branch merging workflows when using this approach. It provides the necessary interface for remote-aware branch analysis and executing secure merge operations directly from your local repository environment.