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.

Jump to install

Repository: docs-as-code-toolkit/architecture-knowledge-toolkit
Last source activity: July 3, 2026 at 15:17
Detected SKILL.md language: English
Stars: 4
Forks: 2

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/docs-as-code-toolkit/architecture-knowledge-toolkit --skill commit-message

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

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.

2026-07-29

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.

2026-07-12

architecture-impact

Analyze and document architecture impact for feature requests, Epic issues, UserStory issues, refactoring tasks, issue implementation, and review tasks. Use when Codex is asked to handle a feature request, decide whether feature work should become an Epic or UserStory, create or refine an Epic, mark a UserStory or refactoring issue, implement feature or refactoring work, review a pull request or review task, assess whether code changes affect architecture documentation, update affected arc42 sections, connect features or refactorings to ADRs, quality goals, quality scenarios, risks, components, runtime scenarios, deployment views, or create follow-up ADRs with diagrams.

2026-07-12

View all from this repository

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.

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

Keep the first line short, with 50 characters or less.
Use the imperative mood, such as Add feature instead of Added feature.
Leave a blank line after the summary when adding a body.
Use the body only when more detail is needed.
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.

commit-message

Source facts

Install options

Review the source files

More from this repository

More from this repository

Commit Message Skill

Purpose

Format

Rules

Issue References

Commit Message Skill

Purpose

Format

Rules

Issue References