AGENT SKILL

commit-message

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
最近更新
2026-11-10
Stars
★ 4
Forks
2

01 前言 Front Matter

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.

03 SKILL.md 正文

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:

issue_<issue number>: <imperative summary>

Example:

issue_123: Add metadata validation

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

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.

04 同仓库更多 Skills

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

traceability-review

Review explicit architecture traceability metadata for gaps, inconsistencies, unsupported claims, stale links, dangling references, and metamodel violations. Use when Codex needs to inspect artifact relations, validate ADR-to-risk or quality-scenario coverage, propose relation updates, or produce an evidence-backed traceability review report.

★ 4
docs-as-code-toolkit
docs-as-code-toolkit/architecture-knowledge-toolkit

slice-issues

Slice GitHub parent issues into reviewable real sub-issues. Use when Codex is asked to split, slice, decompose, refine, or plan a GitHub issue into child issues, sub-issues, implementation slices, or reviewable follow-up issues before implementation work begins.

★ 4
docs-as-code-toolkit
docs-as-code-toolkit/architecture-knowledge-toolkit

risk

Create proposed architecture risk artifacts and analyze their traceability to ADRs, quality scenarios, requirements, components, controls, and evidence. Use when Codex needs to identify, draft, update, prioritize, or review architecture risks, separate risks from issues and decisions, propose mitigations, or produce a risk impact report without deciding acceptance.

★ 4
docs-as-code-toolkit
docs-as-code-toolkit/architecture-knowledge-toolkit

quality-scenario

Create proposed quality scenarios and analyze their traceability to quality objectives, ADRs, risks, requirements, architecture artifacts, and code evidence. Use when Codex needs to draft or update measurable quality scenarios, inspect existing arc42 Chapter 10 quality requirements, derive scenarios from source evidence without inventing targets, propose metadata relations, or produce a quality scenario impact report.

★ 4
docs-as-code-toolkit
docs-as-code-toolkit/architecture-knowledge-toolkit

presentation

Create or update docs-as-code presentation material as AsciiDoc reveal.js decks rendered with docs-toolbox. Use when Codex needs to prepare talks, meetup or conference proposals, speaker notes, demo scripts, event-specific artifacts under talks/, or slide decks that must remain repository-native rather than PowerPoint or Google Slides files.

★ 4
docs-as-code-toolkit
docs-as-code-toolkit/architecture-knowledge-toolkit

pr-review

Review GitHub pull requests and proposed branch changes for correctness, regressions, missing tests, documentation-contract violations, traceability gaps, and reviewability. Use when an AI assistant is asked to review a PR, review pull request changes, inspect a PR branch before merge, or produce PR review comments.

★ 4