Commit

Skill guillempuche/ai-standards/.claude/skills/commit

Open-source AI coding skills for Claude Code, Cursor, Copilot, and AI agents

Install

npx -y skills add guillempuche/ai-standards --skill commit

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Commit workflow for ai-standards repo. Formats all markdown files and previews changes before committing.

SKILL.md

1.6 KB, as published. Nobody here has run it

Commit Workflow

Standard commit workflow for the ai-standards repository.

Before Every Commit

1. Run Markdown Formatter

Format project markdown files using mdformat (excludes opensrc/ which contains external source):

nix develop -c mdformat skills/ .claude/ agents/ templates/ *.md

2. Preview Changes

Show files involved and diff preview:

git status
git diff --stat
git diff

3. Analyze and Group Changes

Review the changes and determine:

Single commit: All changes are related to one feature/fix
Multiple commits: Changes are unrelated and should be separate

Examples:

Docs update + new skill → 2 commits
Rename agent + update references → 1 commit
Bug fix + unrelated refactor → 2 commits

4. Stage and Commit

For single commit:

git add -A
git commit -m "commit message"

For multiple commits, stage selectively:

git add <related-files>
git commit -m "first commit message"

git add <other-files>
git commit -m "second commit message"

Commit Message Guidelines

Start with uppercase, imperative mood
Reference skill/agent names in brackets when applicable: [powersync] Add sync pattern docs

If AI made the changes, include co-author:

Co-Authored-By: Claude <[email protected]>

Output Format

Always show proposed commits with their files:

**Commit 1:** `commit message here`
- file1.md
- file2.ts

**Commit 2:** `another commit message`
- file3.md

Then wait for user approval before executing.

Gives 2 of the 12 instructions most pr commit review skills give

Counted across 888 of the 1,342 authors here whose files we hold, read 2026-08-06

use conventional commits formatin 123 of 888, across 110 files
keep subject line under 72 charactersin 60 of 888, across 46 files
delete branches after mergein 50 of 888, across 37 files
use imperative mood in subject linein 50 of 888, across 41 files
use imperative mood in commit messageshere, and in 45 of 888
generate a conventional commit messagein 42 of 888
make atomic commitsin 37 of 888, across 25 files
run tests before committingin 36 of 888, across 24 files
run project test suite to verify clean baselinein 35 of 888, across 7 files
run detected project setup commandsin 34 of 888, across 6 files
wrap commit body at 72 charactersin 32 of 888, across 25 files
split unrelated changes into separate commitshere, and in 32 of 888, across 27 files

Said here and by no other author read

run markdown formatter before committing
preview changes before committing
reference skill or agent names in brackets

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.