Skip to content
cccskills
FreePublished on 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>`.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md2.1 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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)

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

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.

The English summary is being prepared. Showing the original description.

encero-systems/incan70Updated Oct 19, 2026

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.

The English summary is being prepared. Showing the original description.

encero-systems/incan70Updated Oct 19, 2026

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.

The English summary is being prepared. Showing the original description.

encero-systems/incan70Updated Oct 19, 2026

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.

The English summary is being prepared. Showing the original description.

encero-systems/incan70Updated Oct 19, 2026

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).

The English summary is being prepared. Showing the original description.

encero-systems/incan70Updated Oct 19, 2026

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.

The English summary is being prepared. Showing the original description.

encero-systems/incan70Updated Oct 19, 2026

See all skills by encero-systems

Report a problem with this skill