ck:git
Git operations with conventional commits. Use for staging, committing, pushing, PRs, merges. Auto-splits commits by type/scope. Security scans for secrets.
Best use case
ck:git is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Git operations with conventional commits. Use for staging, committing, pushing, PRs, merges. Auto-splits commits by type/scope. Security scans for secrets.
Teams using ck:git should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/git/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How ck:git Compares
| Feature / Agent | ck:git | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Git operations with conventional commits. Use for staging, committing, pushing, PRs, merges. Auto-splits commits by type/scope. Security scans for secrets.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Git Operations ## Default (No Arguments) If invoked without arguments, use `AskUserQuestion` to present available git operations: | Operation | Description | |-----------|-------------| | `cm` | Stage files & create commits | | `cp` | Stage files, create commits and push | | `pr` | Create Pull Request | | `merge` | Merge branches | Present as options via `AskUserQuestion` 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 | Task | Reference | |------|-----------| | Commit | `references/workflow-commit.md` | | Push | `references/workflow-push.md` | | Pull Request | `references/workflow-pr.md` | | Merge | `references/workflow-merge.md` | | Standards | `references/commit-standards.md` | | Safety | `references/safety-protocols.md` | | Branches | `references/branch-management.md` | | GitHub CLI | `references/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 `.claude` directory (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 | Error | Action | |-------|--------| | Secrets detected | Block commit, show files | | No changes | Exit cleanly | | Push rejected | Suggest `git pull --rebase` | | Merge conflicts | Suggest 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
Related Skills
ck:worktree
Create isolated git worktree for parallel development in monorepos.
ck:web-testing
Web testing with Playwright, Vitest, k6. E2E/unit/integration/load/security/visual/a11y testing. Use for test automation, flakiness, Core Web Vitals, mobile gestures, cross-browser.
ck:web-frameworks
Build with Next.js (App Router, RSC, SSR, ISR), Turborepo monorepos. Use for React apps, server rendering, build optimization, caching strategies, shared dependencies.
ck:web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
ck:watzup
Review recent changes and wrap up the current work session.
ck:use-mcp
Utilize MCP server tools with intelligent discovery and execution.
ck:ui-ux-pro-max
UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples.
ck:ui-styling
Style UIs with shadcn/ui components (Radix UI + Tailwind CSS). Use for accessible components, themes, dark mode, responsive layouts, design systems, color customization.
ck:threejs
Build 3D web apps with Three.js (WebGL/WebGPU). 556 searchable examples, 60 API classes, 20 use cases. Actions: create 3D scene, load model, add animation, implement physics, build VR/XR. Topics: GLTF loader, PBR materials, particle effects, shadows, post-processing, compute shaders, TSL. Integrations: WebGPU, physics engines, spatial audio.
ck:test
Run unit, integration, e2e, and UI tests. Use for test execution, coverage analysis, build verification, visual regression, and QA reports.
ck:template-skill
Replace with description of the skill and when Claude should use it.
ck:team
Orchestrate Agent Teams for parallel multi-session collaboration. Use for research, implementation, review, and debug workflows requiring independent teammates.