Community编程与开发github.com

everyinc/ce-commit

使用清晰、能够传达价值的消息创建 Git 提交。当用户说“提交”、“提交这个”、“保存我的更改”、“创建提交”或想要提交暂存或未暂存的工作时使用。生成结构良好的提交消息,遵循仓库约定(如果存在),否则默认为常规提交格式。

ce-commit 是什么?

everyinc/ce-commit 是一款 AI 代理技能,旨在自动生成高质量的 Git 提交消息。该技能通过分析暂存或未暂存的更改,智能推断出变更的意图,并生成清晰、价值导向的提交消息。它能够识别并遵循仓库中已有的提交约定(如 Conventional Commits、Angular 风格等),若未检测到具体约定,则默认使用 Conventional Commits 格式。这对于希望保持提交历史一致、可读性强的开发者尤为有用,有助于代码审查、变更日志自动生成以及协作效率提升。该技能兼容 Claude Code、Cursor、Codex 等主流 AI 代理平台,可无缝集成到日常开发工作流中。其核心优势在于减少了手动编写提交消息的认知负担,同时确保了消息的专业性和规范性。

兼容平台~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/everyinc/compound-engineering-plugin/tree/main/skills/ce-commit

Installed? Explore more 编程与开发 skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →

在你喜欢的 AI 中提问

打开一个已预加载此 Agent Skill 的新对话。

文档

ce-commit 是做什么的?

使用清晰、能够传达价值的消息创建 Git 提交。当用户说“提交”、“提交这个”、“保存我的更改”、“创建提交”或想要提交暂存或未暂存的工作时使用。生成结构良好的提交消息,遵循仓库约定(如果存在),否则默认为常规提交格式。

工作原理

该技能通过分析 git diff 和 git log 的输出来确定更改的性质和范围。它会检查仓库中是否存在约定(如 .gitmessage、commitlint.config.js、conventional-changelog 配置等),并相应地调整提交消息格式。如果检测到约定,则遵循该约定;否则,默认使用 Conventional Commits 格式(例如 feat:, fix:, chore: 等前缀)。

使用方法

暂存工作

# 用户说“提交”时,技能会自动暂存所有更改(包括未暂存的)
git add -A
git commit -m "feat: add user authentication module"

仅暂存的工作

# 如果用户已手动暂存更改,技能会直接创建提交
git commit -m "fix: resolve login timeout issue"

配置

该技能不需要额外配置。它会自动检测仓库约定并生成合适的提交消息。你也可以通过以下方式覆盖默认行为:

  • 在 .gitmessage 文件中定义提交模板
  • 使用 commitlint 配置来指定提交约定
  • 在 package.json 中设置 commitizen 的配置

支持平台

  • Claude Code
  • Cursor
  • Codex
  • 其他兼容 AI 代理的 Git 工作流

示例

用户输入: “提交我的更改”

技能响应:

✔ 已暂存并提交所有更改

提交消息:refactor(api): streamline endpoint response structure

- 统一了所有端点的响应格式
- 移除了冗余的错误处理逻辑
- 更新了相关的单元测试

用户输入: “创建一个关于修复漏洞的提交”

技能响应:

✔ 已创建提交

提交消息:fix(database): correct connection pool exhaustion error

- 修复了连接池耗尽时未正确处理的问题
- 添加了连接超时重试机制
- 更新了连接池监控日志

许可

MIT

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

everyinc/ce-agent-native-architecture

Build applications where agents are first-class citizens. Use this skill when designing autonomous agents, creating MCP tools, implementing self-modifying systems, or building apps where features are outcomes achieved by agents operating in a loop.

everyinc/ce-agent-native-audit

Run comprehensive agent-native architecture review with scored principles

everyinc/ce-brainstorm

Explore requirements and approaches through collaborative dialogue, then write a right-sized requirements document. Use when the user says "let's brainstorm", "what should we build", or "help me think through X", presents a vague or ambitious feature request, or seems unsure about scope or direction -- even without explicitly asking to brainstorm.

everyinc/ce-clean-gone-branches

Clean up local branches whose remote tracking branch is gone. Use when the user says "clean up branches", "delete gone branches", "prune local branches", "clean gone", or wants to remove stale local branches that no longer exist on the remote. Also handles removing associated worktrees for branches that have them.

everyinc/ce-code-review

Structured code review using tiered persona agents, confidence-gated findings, and a merge/dedup pipeline. In interactive mode it applies safe, verified fixes and commits them when the working tree is clean (it never pushes); in mode:agent it reports only and the caller applies. Use when reviewing code changes before creating a PR.

everyinc/ce-commit-push-pr

Commit, push, and open a PR with an adaptive, value-first description that scales in depth with the change. Use when the user says "commit and PR", "ship this", "create a PR", or "open a pull request". Also handles description-only flows ("write a PR description", "rewrite the PR body", "describe this PR") without committing or pushing.

everyinc/ce-compound

Document a recently solved problem to compound your team's knowledge or CONCEPTS.md, the project's shared domain vocabulary.

everyinc/ce-compound-refresh

Refresh stale learning and pattern docs under docs/solutions/ by reviewing them against the current codebase, then updating, consolidating, or deleting drifted ones. Use when the user asks to "refresh my learnings", "audit docs/solutions/", "clean up stale learnings", or "consolidate overlapping docs", or when ce-compound flags an older doc as superseded. Do not trigger for general refactor, debugging, or code-review work unless the user has explicitly pointed at docs/solutions/.

everyinc/ce-debug

Systematically find root causes and fix bugs. Use when debugging errors, investigating test failures, reproducing bugs from issue trackers (GitHub, Linear, Jira), or when stuck on a problem after failed fix attempts. Also use when the user says 'debug this', 'why is this failing', 'fix this bug', 'trace this error', or pastes stack traces, error messages, or issue references.

everyinc/ce-demo-reel

Capture a visual demo reel (GIF, terminal recording, screenshots) for PR descriptions. Use when shipping UI changes, CLI features, or any work with observable behavior that benefits from visual proof. Also use when asked to add a demo, record a GIF, screenshot a feature, show what changed visually, create a demo reel, capture evidence, add proof to a PR, or create a before/after comparison.

everyinc/ce-dhh-rails-style

This skill should be used when writing Ruby and Rails code in DHH's distinctive 37signals style. It applies when writing Ruby code, Rails applications, creating models, controllers, or any Ruby file. Triggers on Ruby/Rails code generation, refactoring requests, code review, or when the user mentions DHH, 37signals, Basecamp, HEY, or Campfire style. Embodies REST purity, fat models, thin controllers, Current attributes, Hotwire patterns, and the "clarity over cleverness" philosophy.

everyinc/ce-doc-review

Review requirements or plan documents using parallel persona agents that surface role-specific issues. Use when a requirements document or plan document exists and the user wants to improve it.

everyinc/ce-frontend-design

Build web interfaces with genuine design quality, not AI slop. Use for any frontend work - landing pages, web apps, dashboards, admin panels, components, interactive experiences. Activates for both greenfield builds and modifications to existing applications. Detects existing design systems and respects them. Covers composition, typography, color, motion, and copy. Verifies results via screenshots before declaring done.

everyinc/ce-gemini-imagegen

This skill should be used when generating and editing images using the Gemini API (Nano Banana Pro). It applies when creating images from text prompts, editing existing images, applying style transfers, generating logos with text, creating stickers, product mockups, or any image generation/manipulation task. Supports text-to-image, image editing, multi-turn refinement, and composition from multiple reference images.

everyinc/ce-ideate

Generate and critically evaluate grounded ideas about a topic. Use when asking what to improve, requesting idea generation, exploring surprising directions, or wanting the AI to proactively suggest strong options before brainstorming one in depth. Triggers on phrases like 'what should I improve', 'give me ideas', 'ideate on X', 'surprise me', 'what would you change', or any request for AI-generated suggestions rather than refining the user's own idea.

everyinc/ce-optimize

Run metric-driven iterative optimization loops -- define a measurable goal, run parallel experiments, measure each against hard gates or LLM-as-judge scores, keep improvements, and converge on the best solution. Use when optimizing clustering quality, search relevance, build performance, prompt quality, or any measurable outcome that benefits from systematic experimentation.

everyinc/ce-plan

Create structured plans for multi-step tasks -- software features, research workflows, events, study plans, or any goal that benefits from breakdown. Also deepens existing plans with interactive sub-agent review. Use when the user says 'plan this', 'create a plan', 'how should we build', 'break this down', or when a brainstorm doc is ready for planning. Use 'deepen the plan' or 'deepening pass' for the deepening flow. For exploratory requests, prefer ce-brainstorm first.

everyinc/ce-polish-beta

[BETA] Start the dev server, open the feature in a browser, and iterate on improvements together.

everyinc/ce-product-pulse

Generate a time-windowed pulse report on what users experienced and how the product performed - usage, quality, errors, signals worth investigating. Use when the user says 'run a pulse', 'show me the pulse', 'how are we doing', 'weekly recap', 'launch-day check', or passes a time window like '24h' or '7d'. Configures via .compound-engineering/config.local.yaml and saves reports to docs/pulse-reports/.

everyinc/ce-proof

Publish, view, comment on, and edit markdown via Proof (proofeditor.ai) — create a shareable doc, read a shared doc, and make comment/suggestion/block edits over its API. Use when the user says "view this in proof", "share to proof", "publish to proof", or wants a shareable markdown surface for a spec, plan, or draft, including publish handoffs from ce-brainstorm, ce-ideate, or ce-plan. Do not trigger on "proof" meaning evidence, math proofs, proof-of-concept, or "proofread this".

相关技能