CE Commit Assistant
Create git commits with clear, value-communicating messages that state the outcome.
The skill explicitly limits itself to local commits, prohibits push and PR, avoiding overreach; it stages only named files and forbids git add -A or git add ., following least privilege. No sensitive data handling or external network calls. However, no explicit user confirmation step is declared, though branch creation may be automatic; publisher identity unverified, and no rollback mechanism described. Therefore not full marks.
Instructions are internally consistent, with clear context-gathering commands and failure interpretation table, and explicit handling of non-zero exits. But no test coverage for the skill's key path, e.g., no test that directly exercises ce-commit. Static assessment cannot confirm reproducibility on all platforms. Hence below 10.
Clear use case: trigger when user asks to commit changes. Boundaries: only commit, not push/PR. But trigger might be imprecise in complex scenarios, e.g., user may expect single commit but skill creates multiple logical commits. Environment fit: skill aims cross-platform, but no mention of mainland China network reachability; skill does not depend on overseas services, so unaffected. However, missing handling of out-of-scope scenarios like explicit push request.
Documentation is well-structured with clear name, description, usage, workflow, and examples. README provides comprehensive install instructions and changelog links. But specific changelog file not inspected; version visible in package.json but skill itself lacks version. Maintenance responsibility partially addressed in SECURITY.md, but update path for skill itself unclear. Deduction applied.
Skill can complete commit task with clear message. But lack of verifiable typical output and execution evidence; static read cannot confirm effectiveness. Marginal value in auto-generating conventional commit messages, but may be less than manual control. Hence below 7.
Repo CI covers converters and plugin validation but no dedicated tests for ce-commit. Examples and instructions are auditable but lack independent reproduction evidence. Hence below 5.
- Publisher identity unverified; source credibility uncertain.
- Skill does not explicitly require user confirmation, especially automatic branch creation may exceed user expectations.
- No dedicated test coverage for ce-commit skill itself, reliability unverified.
- No mention of mainland China network reachability, but skill has no external dependencies, so limited impact.
- Changelog file not provided, version history incomplete.
What does this skill do, and when should you use it?
This is a skill within the Compound Engineering plugin bundle focused on local git commits. It helps users commit their working tree changes in logical groups with messages that follow project conventions. By gathering repository status, checking branch and recent log style, it derives an appropriate commit convention (like conventional commits) and guides the user to stage and commit named files safely, without using `git add -A`. It does not push or create PRs — it only handles local commits. It emphasizes checking workspace state before committing and creating a feature branch if on the default branch or detached HEAD.
Runs a series of shell commands (git status, git diff HEAD, git branch --show-current, git log --oneline -10, git rev-parse --abbrev-ref origin/HEAD) to gather repository context; checks if working tree is clean; creates a feature branch if on default branch or detached HEAD; generates commit message based on project history or conventional commits; stages only named files (never git add -A or .); executes git add and git commit; finally confirms git status and reports commit hash(es) and subject(s).
- A developer completes a feature or fix and wants to commit with a clear, meaningful message locally.
- When working in a large codebase, a developer wants to split changes into logical commits (e.g., fix vs. feature).
- A developer wants to follow the project's existing commit style or conventional commits.
- A developer is on the default branch or detached HEAD and needs to create a feature branch before committing.
- A developer wants precise control over what gets staged without using `git add -A`.
What are this skill's strengths and limitations?
- Generates clear, outcome-focused commit messages automatically.
- Encourages breaking changes into multiple logical commits.
- Automatically handles creating a branch if on default branch or detached HEAD.
- Does not push or create PRs, suitable for local workflow.
- Only offers file-level grouping; does not support partial staging like `git add -p`.
- Requires shell access and git commands, which may be limited in certain environments.
- Not tested on platforms that don't support shell commands, like some chat interfaces.
How do you install this skill?
This skill is part of the Compound Engineering plugin. Installation varies by client: for Claude Code, use /plugin marketplace add EveryInc/compound-engineering-plugin and /plugin install compound-engineering; for Cursor, use /add-plugin compound-engineering; for Codex CLI, use codex plugin marketplace add EveryInc/compound-engineering-plugin and codex plugin add compound-engineering@compound-engineering-plugin; other clients (Kimi, Cline, Grok, etc.) have similar steps. See the README for full details.
How do you use this skill?
In a repository, ask the AI assistant to 'commit these changes' or 'git commit'. The skill will automatically run the context-gathering steps and then create the commit based on the prompt. If uncertain, it will ask or follow the established workflow.