cc

Name: cc
Availability: InStock
Author: Luke

Create a Git commit with Conventional Commits formatting from current worktree changes.

Updated Aug 23, 2026

Search Tags:#git #workflow #commit #worktree #staging #version-control #conventional-commit

Ready to run

npx skills add https://github.com/lc0rp/luke-agent-scripts --skill cc-lc0rp

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cc
Source: https://github.com/lc0rp/luke-agent-scripts/tree/main/skills/cc
Command: npx skills add https://github.com/lc0rp/luke-agent-scripts --skill cc-lc0rp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze the current git worktree and turn changes into a conventional commit, ensuring messaging clarity, proper staging, and automated commit creation.

Core Features & Use Cases

Inspect the worktree state and read relevant diffs before composing a message.
Determine whether changes form one coherent commit and generate a conventional commit message.
Stage the right files and create the commit, returning the final commit SHA and status.

Quick Start

Ask Codex to inspect the current worktree and create a conventional commit from the changes.

Frequently Asked Questions about cc

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I create a conventional commit from git worktree changes?▼

A conventional commit tool inspects git worktree status and diffs, validates change coherence, stages relevant files, and writes a structured commit message using non-interactive git commands without manual editing.

How do I automatically stage and commit git changes with a valid message?▼

Automated git staging and committing tools inspect worktree diffs, validate change coherence, stage relevant files, and generate conventional commit messages using non-interactive git commands.

What is a conventional commit message and how is it generated from a diff?▼

Conventional commit messages follow a structured format generated by inspecting git worktree diffs, validating change coherence, and auto-writing standardized commit text using non-interactive git commands.

Can I automate git commit message writing without interactive prompts?▼

Yes, automated conventional commit tools use non-interactive git commands to inspect worktree changes, stage files, and create commits with auto-generated messages without requiring interactive editor prompts.

Does automated committing validate whether my staged changes form one coherent commit?▼

Yes, conventional commit tools inspect git status and diffs to validate change coherence, ensuring worktree modifications form one logical commit before staging files and writing the commit message.

What are the limitations of auto-generating git commits from worktree changes?▼

Auto-generating git commits from worktree changes assumes coherent modifications exist in the current repository and may not handle complex multi-purpose changes or granular interactive staging scenarios effectively.