How do I install the Authoring Commits skill?

Run npx skillmds add majiayu000/authoring-commits in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Authoring Commits safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Authoring Commits?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Authoring Commits free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Authoring Commits?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Authoring Commits by majiayu000 — Agent Skill

Name: Authoring Commits
Rating: 4.5 (4 reviews)
Author: majiayu000

File contents

Commit Authoring

Write commit messages following Conventional Commits v1.0.0.

Message Structure

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

Rules

Prefix with type, optional scope in parentheses, optional ! for breaking changes, colon, space
feat for new features (MINOR in SemVer)
fix for bug fixes (PATCH in SemVer)
Description immediately follows the colon and space
Body separated by one blank line, free-form
Footers one blank line after body, token-separator-value format
Footer tokens use - instead of spaces (except BREAKING CHANGE)
! before : indicates breaking change; BREAKING CHANGE: footer may be omitted if ! is used
Breaking changes correlate with MAJOR in SemVer

Types

Type	Purpose	SemVer
`feat`	New feature	MINOR
`fix`	Bug fix	PATCH
`docs`	Documentation only	-
`style`	Formatting, whitespace	-
`refactor`	Neither fix nor feature	-
`perf`	Performance improvement	-
`test`	Adding or updating tests	-
`build`	Build system or dependencies	-
`ci`	CI configuration	-
`chore`	Maintenance tasks	-

Description

Use imperative mood: "add feature" not "added feature". Keep under 50 characters. No period. Lowercase after type prefix.

Body

Wrap at 72 characters. Explain what and why, not how.

Prohibited

Do not include "Generated with Claude Code", AI attribution, Co-authored-by lines for AI, emoji, time estimates, dates, or TODO items.

Examples

Simple:

docs: correct spelling of CHANGELOG

With scope:

feat(lang): add Polish language

Breaking change:

feat!: send email to customer when product ships

BREAKING CHANGE: customers now receive emails by default.

With body:

fix: prevent duplicate form submissions

Disables submit button after first click and adds
debounce to the handler.

With footer:

fix: resolve race condition in auth flow

Refs: #123
Reviewed-by: Alice

---name: authoring-commitsdescription: Conventional Commits standards for git messages. Use when creating commits, writing commit messages, or reviewing commit history.--- # Commit Authoring Write commit messages following Conventional Commits v1.0.0. ## Message Structure ``` <type>[optional scope]: <description> [optional body] [optional footer(s)] ``` ## Rules 1. Prefix with type, optional scope in parentheses, optional `!` for breaking changes, colon, space 2. `feat` for new features (MINOR in SemVer) 3. `fix` for bug fixes (PATCH in SemVer) 4. Description immediately follows the colon and space 5. Body separated by one blank line, free-form 6. Footers one blank line after body, token-separator-value format 7. Footer tokens use `-` instead of spaces (except `BREAKING CHANGE`) 8. `!` before `:` indicates breaking change; `BREAKING CHANGE:` footer may be omitted if `!` is used 9. Breaking changes correlate with MAJOR in SemVer ## Types | Type | Purpose | SemVer | |------|---------|--------| | `feat` | New feature | MINOR | | `fix` | Bug fix | PATCH | | `docs` | Documentation only | - | | `style` | Formatting, whitespace | - | | `refactor` | Neither fix nor feature | - | | `perf` | Performance improvement | - | | `test` | Adding or updating tests | - | | `build` | Build system or dependencies | - | | `ci` | CI configuration | - | | `chore` | Maintenance tasks | - | ## Description Use imperative mood: "add feature" not "added feature". Keep under 50 characters. No period. Lowercase after type prefix. ## Body Wrap at 72 characters. Explain what and why, not how. ## Prohibited Do not include "Generated with Claude Code", AI attribution, Co-authored-by lines for AI, emoji, time estimates, dates, or TODO items. ## Examples Simple: ``` docs: correct spelling of CHANGELOG ``` With scope: ``` feat(lang): add Polish language ``` Breaking change: ``` feat!: send email to customer when product ships BREAKING CHANGE: customers now receive emails by default. ``` With body: ``` fix: prevent duplicate form submissions Disables submit button after first click and adds debounce to the handler. ``` With footer: ``` fix: resolve race condition in auth flow Refs: #123 Reviewed-by: Alice ```

Frequently asked questions