ccp

Analyze git worktree changes, stage files, and create a conventional commit.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/lc0rp/luke-agent-scripts --skill ccp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ccp
Source: https://github.com/lc0rp/luke-agent-scripts/tree/main/skills/ccp
Command: npx skills add https://github.com/lc0rp/luke-agent-scripts --skill ccp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill analyzes the current git worktree to understand the real intent behind changes and turns them into a conventional commit, then stages the appropriate files, creates the commit, and pushes the current branch.

Core Features & Use Cases

  • Inspect git state (staged and unstaged changes) and read diffs to infer intent.
  • Generate a conventional commit message that matches the actual change.
  • Stage the correct files, create the commit, and push the current branch.
  • Use case: when you want to reliably turn local changes into a clean, conventional commit and push it to the remote.

Quick Start

Tell Codex to inspect the current worktree, generate a conventional commit message from the changes, stage the right files, commit them, and push the branch.

Frequently Asked Questions about ccp

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

FAQPage Schema
How do I automatically generate conventional commit messages from git worktree changes?

This skill inspects your local git worktree state, reads the diffs of staged and unstaged changes to understand the real intent, stages the correct files, and creates a commit with a conventional message.

Can I stage and push unstaged git changes in a single step?

Yes, you can stage and push unstaged git changes in a single step. The skill analyzes the mixed git state, stages the appropriate files, creates a conventional commit, and pushes the current branch to the remote.

What happens when I have mixed staged and unstaged git changes?

When you have mixed staged and unstaged git changes, the skill analyzes the worktree to ensure a coherent single commit, or it prompts you to split the commit when the changes do not fit together logically.

Does this work with standard git workflows to create and push a conventional commit?

It integrates with standard git workflows by inspecting the current worktree, staging the appropriate files, creating a conventional commit, and pushing the current branch to the remote repository automatically.

Why should I use an automated conventional commit generator instead of manual git staging?

Using an automated conventional commit generator instead of manual git staging ensures the commit message accurately reflects the diff intent, reducing human error and maintaining a clean, conventional commit history.