Skip to content
Agentmart
Submit a tool

commit-message

Write repository commit messages.

Skill by docs-as-code-toolkit

IndexedMIT★ 4
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/docs-as-code-toolkit-commit-message

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Write repository commit messages. Use when an agent creates commits, prepares commit text, reviews commit history, or updates workflow guidance that mentions commit messages.

Use cases: writing, productivity, agent-building

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/commit-message

What's inside

Skill name
commit-message
Description
Write repository commit messages. Use when an agent creates commits, prepares commit text, reviews commit history, or updates workflow guidance that mentions commit messages.
License
MIT
Instructions
42 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Commit Message Skill

## Purpose

Write clear, traceable commit messages for this repository without assuming a
specific AI engine or runtime.

## Format

For work done for an issue, start the summary with the issue number:

```text
issue_<issue number>: <imperative summary>
```

Example:

```text
issue_123: Add metadata validation
```

For work that does not refer to an issue, start directly with the imperative
summary:

```text
Add metadata validation
```

## Rules

1. Keep the first line short, with 50 characters or less.
2. Use the imperative mood, such as `Add feature` instead of `Added feature`.
3. Leave a blank line after the summary when adding a body.
4. Use the body only when more detail is needed.
5. Describe why the change was made, not only what changed.

## Issue References

Use the `issue_<issue number>:` prefix only when the commit belongs to a known
issue. Do not invent an issue number.

From docs-as-code-toolkit/architecture-knowledge-toolkit, MIT.

More from docs-as-code-toolkit/architecture-knowledge-toolkit

Signals

Stars
4
Forks
2
Open issues
44
Last commit (this folder)
Jul 3, 2026 (3 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from docs-as-code-toolkit

Cite this page

commit-message skill. Agent Mart. https://agentmart.dev/skills/docs-as-code-toolkit-commit-message (last updated 2026-10-24)