Ck:Git logo

Ck:Git

Community
manhvann
ck:git

Git operations with conventional commits. Use for staging, committing, pushing, PRs, merges. Auto-splits commits by type/scope. Security scans for secrets.

Overview

Publishermanhvann
Repositorycodexkit
Skill nameck:git
Stars
88
Forks
81
Bundled files
8
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 8 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by manhvann on GitHub. Read the source before you install it.

Installation

Install the Ck:Git AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/manhvann/codexkit/tree/main/.agents/skills/git
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/manhvann/codexkit.git /tmp/codexkit
mkdir -p .claude/skills
cp -r /tmp/codexkit/.agents/skills/git .claude/skills/manhvann-ck-git
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Ck:Git in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Ck:Git on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Ck:Git is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Git Operations

Default (No Arguments)

If invoked without arguments, ask the user to choose available git operations:

OperationDescription
cmStage files & create commits
cpStage files, create commits and push
prCreate Pull Request
mergeMerge branches

Present options with header "Git Operation", question "What would you like to do?".

Execute git workflows via git_manager subagent to isolate verbose output. Activate ck:context-engineering skill.

IMPORTANT:

  • Sacrifice grammar for the sake of concision.
  • Ensure token efficiency while maintaining high quality.
  • Pass these rules to subagents.

Arguments

  • cm: Stage files & create commits
  • cp: Stage files, create commits and push
  • pr: Create Pull Request [to-branch] [from-branch]
    • to-branch: Target branch (default: main)
    • from-branch: Source branch (default: current branch)
  • merge: Merge [to-branch] [from-branch]
    • to-branch: Target branch (default: main)
    • from-branch: Source branch (default: current branch)

Quick Reference

TaskReference
Commitreferences/workflow-commit.md
Pushreferences/workflow-push.md
Pull Requestreferences/workflow-pr.md
Mergereferences/workflow-merge.md
Standardsreferences/commit-standards.md
Safetyreferences/safety-protocols.md
Branchesreferences/branch-management.md
GitHub CLIreferences/gh-cli-guide.md

Core Workflow

Step 1: Stage + Analyze

bash
git add -A && git diff --cached --stat && git diff --cached --name-only

Step 2: Security Check

Scan for secrets before commit:

bash
git diff --cached | grep -iE "(api[_-]?key|token|password|secret|credential)"

If secrets found: STOP, warn user, suggest .gitignore.

Step 3: Split Decision

NOTE:

  • Search for related issues on GitHub and add to body.
  • Only use feat, fix, or perf prefixes for files in .codex or .agents directories (do not use docs).

Split commits if:

  • Different types mixed (feat + fix, code + docs)
  • Multiple scopes (auth + payments)
  • Config/deps + code mixed
  • FILES > 10 unrelated

Single commit if:

  • Same type/scope, FILES ≤ 3, LINES ≤ 50

Step 4: Commit

bash
git commit -m "type(scope): description"

Output Format

✓ staged: N files (+X/-Y lines)
✓ security: passed
✓ commit: HASH type(scope): description
✓ pushed: yes/no

Error Handling

ErrorAction
Secrets detectedBlock commit, show files
No changesExit cleanly
Push rejectedSuggest git pull --rebase
Merge conflictsSuggest manual resolution

References

  • references/workflow-commit.md - Commit workflow with split logic
  • references/workflow-push.md - Push workflow with error handling
  • references/workflow-pr.md - PR creation with remote diff analysis
  • references/workflow-merge.md - Branch merge workflow
  • references/commit-standards.md - Conventional commit format rules
  • references/safety-protocols.md - Secret detection, branch protection
  • references/branch-management.md - Naming, lifecycle, strategies
  • references/gh-cli-guide.md - GitHub CLI commands reference

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Ck:Git AI skill do?

Git operations with conventional commits. Use for staging, committing, pushing, PRs, merges. Auto-splits commits by type/scope. Security scans for secrets.

Why use Ck:Git on TypingMind?

Because you install it once and use it with any model. Ck:Git is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Ck:Git in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/manhvann/codexkit/tree/main/.agents/skills/git. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Ck:Git?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Ck:Git?

As many as you like. As long as a model supports skills, you can use Ck:Git with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Ck:Git AI skill free?

Yes. It is published on GitHub by manhvann under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇