跳到正文
cccskills
免费在 GitHub 公开

write-commit-message

Draft commit titles and optional commit bodies using the workspace commit naming convention. Use when the user asks for a commit message, commit text, commit title, or wants commit wording in the format `chore|bugfix|feature - <issue_id(s)> <short description>`.

中文简介正在准备中。当前显示原文说明。

encero-systems/incan
查看安装方法

包含的文件（1）

  • SKILL.md2.1 KB

SKILL.md（原文）

安装前可以查看交给 AI 代理的指令内容。

Write Commit Message

Workflow

  1. Identify the repository and inspect the actual change set before drafting anything.
  2. Infer the change type from the diff:
    • bugfix for correctness fixes and regressions
    • feature for new behavior or newly implemented surface area
    • chore for maintenance, docs-only changes, refactors without new behavior, or repository housekeeping
  3. Infer issue ids from the branch name first, then from explicit issue references in the current task context if needed.
  4. Write the title in exactly this format:
<type> - <short description> (<#issue_id(s)>)
  1. Keep the short description concrete:
    • specific to the actual diff
    • no trailing punctuation
    • no vague filler like updates or misc fixes
  2. If the user also wants a commit body, write:
    • one short sentence on what changed
    • one short sentence on why
    • optional flat bullets only if there are multiple distinct changes worth calling out

Issue Id Rules

  • Use numeric ids joined by commas when there are multiple issues:
bugfix - preserve method result types for locals bound from calls (#252, #255)
  • Do not prepend # unless the user explicitly asks for that style.
  • If no issue id is discoverable, say so instead of inventing one.

Output Rules

  • If the user asks for a commit message or commit text, return the commit title by itself unless they also asked for a body.
  • If the user asks for both, return the title first and then the body.
  • Do not wrap the final title in commentary.
  • If the requested type conflicts with the actual diff, follow the diff and say so.

Examples

bugfix - preserve something important for locals bound from calls (#42)

feature - add Session builder and DataFusion backend seam (#5)

chore - tighten RFC 008 optimizer boundary wording (#18)

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护，适用 Google 的隐私权政策和服务条款。

同一仓库的技能

add-learning

免费

Add a new learning to the agent learnings file. Use when the user says /add-learning, asks to record a lesson, or when an implementation produced a reusable insight worth preserving for future agents.

中文简介正在准备中。当前显示原文说明。

encero-systems/incan652026年10月19日 更新

bump-rfc

免费

Transition an Incan RFC from one status to the next. Use when the user asks to promote, advance, or finalize an RFC, or says /bump-rfc. Handles Draft → Planned, Planned → In Progress, and In Progress → Implemented transitions.

中文简介正在准备中。当前显示原文说明。

encero-systems/incan652026年10月19日 更新

closeout

免费

Safely close out completed Incan work after a PR is merged by verifying merge status, syncing the base branch, removing task-owned local worktrees/assets, deleting merged local/remote branches, pruning refs, and reporting dirty or ambiguous leftovers. Use when the user says /closeout, asks to clean up after a merged PR, or wants local RFC/issue branch/worktree cleanup.

中文简介正在准备中。当前显示原文说明。

encero-systems/incan652026年10月19日 更新

create-github-issue

免费

Drafts a GitHub issue title and body using the target repository's issue templates under .github/ISSUE_TEMPLATE. Use when the user asks to create, draft, or file a GitHub issue, bug report, feature request, chore, documentation issue, or RFC proposal, or wants issue text that matches the repo's template.

中文简介正在准备中。当前显示原文说明。

encero-systems/incan652026年10月19日 更新

create-plan

免费

Drafts implementation plans with TDD, documentation updates, and repository verification commands before coding. Use when the user asks for an implementation plan, /create-plan, or structured pre-implementation design for work in encero workspaces (e.g. Incan, IncQL).

中文简介正在准备中。当前显示原文说明。

encero-systems/incan652026年10月19日 更新

create-pr-description

免费

Generate a PR description following the repository's pull request template. Use when the user asks to create, draft, or generate a PR description for a pull request. The skill automatically locates the PR template in the target repository and fills it in based on the git diff.

中文简介正在准备中。当前显示原文说明。

encero-systems/incan652026年10月19日 更新

查看 encero-systems 的全部技能

报告此技能的问题