本文へ移動
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（原文）

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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)

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

ログインしてレビューを書く

同じリポジトリのスキル

概要と使いどころ

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/incan612026年10月11日 更新

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/incan612026年10月11日 更新

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/incan612026年10月11日 更新

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/incan612026年10月11日 更新

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/incan612026年10月11日 更新

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/incan612026年10月11日 更新

encero-systems のスキルをすべて見る

このスキルの問題を報告する