ck:git

Automate Git staging, committing, pushing, and pull requests with conventional commits and security scans.

1|Updated May 4, 2026
One-click install
npx skills add https://github.com/auxi-wardrobe/auxi-all-in --skill ck-git-auxi-wardrobe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:git
Source: https://github.com/auxi-wardrobe/auxi-all-in/tree/main/.agents/skills/git
Command: npx skills add https://github.com/auxi-wardrobe/auxi-all-in --skill ck-git-auxi-wardrobe

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill unit simplifies Git workflows by automating common tasks like staging, committing, pushing, and creating pull requests. It ensures that commits follow conventional commit standards and scans for potential security risks like secrets.

Core Features & Use Cases

  • Conventional Commits:自动分割提交以遵循类型/范围。
  • Security Scans:扫描潜在的安全风险,如机密信息。
  • Automated Workflows:自动化常规任务,提高效率。
  • Use Case:适用于开发人员和管理员,通过自动化Git操作来提高协作效率和代码质量。

Quick Start

Use the 'ck:git' skill to stage and commit your changes, then push them to the remote repository.

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 to follow conventional commit standards?

Automating Git commits to follow conventional commit standards requires splitting staged changes by type and scope. This Skill automatically parses your changes and formats the commit message to adhere to conventional commit rules.

Can I scan for security secrets before pushing to a remote repository?

Yes, you can scan for security secrets before pushing to a remote repository. This Skill automatically inspects staged changes for potential security risks, preventing sensitive information from being committed.

What is the best way to automate staging, committing, and creating pull requests?

The best way to automate staging, committing, and creating pull requests is using an automated Git workflow tool. This Skill handles the entire sequence from staging files to generating pull requests on your remote repository.

Does this Git automation tool work without additional version control dependencies?

No, this Git automation tool does not work without dependencies. It requires Git and associated version control tools to be installed in your environment to execute staging, pushing, and pull request operations.

Why should I use conventional commits in my software development workflow?

You should use conventional commits in your software development workflow to improve collaboration efficiency and code quality. Standardized commit types and scopes make project history readable and automation-friendly.

Are there limitations when automating Git operations for large repositories?

Automating Git operations for large repositories requires sufficient system resources for security scanning and staging. While it handles standard development workflows, extremely large changesets may impact processing time before pushing.