Menu

Individual skill

dev-commit-writer

Write a commit message from a requested Git diff when the user asks for message generation. Does not review, stage, or commit. Requests such as 帮我 commit require the commit workflow, including review when required; asking for a message does not require an explicit skip-review declaration.

plugins/Jason-chen-coder/dev-skills/skills/dev-commit-writer/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,532
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Dev Commit Writer

Produce an accurate, concise commit message in the repository's style. This is a read-only writing task, not a quality verdict or authorization to run `git commit`.

## Load baseline

Read [references/dev-baseline.md](references/dev-baseline.md) before execution. Resolve paths relative to this skill directory.

## Read the intended change

- Identify the actual repository root and inspect status, staged diff, unstaged diff, and recent commit subjects/bodies.
- Honor explicit `--staged` / `--cached`, `--path=<glob>`, named files, and exclusions. Without an explicit scope, use the staged diff when present; otherwise use changes attributable to the task. State the chosen scope briefly if mixed changes could cause confusion.
- Include untracked files only when they belong to the requested change and their content has been inspected. Never silently fold unrelated unstaged work into a message for the index.
- If there is no change to describe, say so. A user-provided diff is also a valid source, but do not pretend to have inspected a local repository when only that text is available.