Commit

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

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

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.

SKILL.md

1.6 KB, 378 tokens by cl100k_base, 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.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 1 of the 12 instructions most pr commit review skills give in 378 tokens

Counted across 1,055 of the 1,911 authors here whose files we hold, read 2026-09-06

Use conventional commit message formatin 150 of 1055, across 145 files
Announce skill usage at startin 78 of 1055
Use imperative mood for commit descriptionshere, and in 54 of 1055, across 51 files
Add directory to gitignore if not ignoredin 52 of 1055, across 41 files
Use imperative mood for commit subjectin 52 of 1055
Run tests to verify clean baselinein 42 of 1055, across 32 files
Push branch to originin 40 of 1055, across 38 files
Verify worktree directory is ignored before creationin 39 of 1055, across 32 files
Delete branches after mergingin 38 of 1055, across 30 files
Create worktree with new branchin 37 of 1055, across 32 files
Wrap body text at 72 charactersin 36 of 1055, across 34 files
Auto-detect and run project setupin 35 of 1055, across 27 files

Said here and by no other author read

Format markdown files using mdformat
Run git status to preview changes
Review changes for logical grouping
Reference skill or agent names in brackets
Include co-author for AI changes

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.