Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

Commencer

commit

Étoiles0

Forks0

Mis à jour21 mars 2026 à 06:53

Generate a commit message and create the commit in one step.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

im9

im9/inboil

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	commit
description	Generate a commit message and create the commit in one step.
allowed-tools	Bash(git diff ), Bash(git status ), Bash(git log ), Bash(git add ), Bash(git commit *)

Commit

Analyze current changes, generate a commit message, stage relevant files, and commit.

Process

Run git diff (unstaged) and git diff --cached (staged) to see all changes.
Run git status -u to see untracked files.
Run git log --oneline -5 to match the repository's commit style.
Analyze all changes and draft a commit message.
Stage relevant files (git add — prefer specific files over -A).
Create the commit.

Commit Message Format

First line: type: short summary (under 72 chars)
- Types: feat, fix, refactor, style, docs, chore
Blank line, then bullet-point details for non-trivial changes
End with Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
If changes span multiple concerns (e.g. a bug fix AND a feature), use multiple type: paragraphs in the body
Write in English (per CLAUDE.md conventions)
Pass the message via HEREDOC for proper formatting

Safety

Never stage files that may contain secrets (.env, credentials, etc.)
Never use git add -A — always add specific files
Never push to remote — only commit locally

Plus depuis ce dépôt

même dépôt

release

im9/inboil

Bump version, generate changelog draft, tag, and deploy a release.

2026-04-030

im9/inboil

Create a feature branch, commit changes, push, and open a PR to main.

2026-03-310

check-docs

im9/inboil

Check docs/ai/ spec files and ADRs for inconsistencies with the actual codebase. Report only, no modifications.

2026-03-280

sync-docs

im9/inboil

Check docs/ai/ spec files and ADRs for inconsistencies with the codebase, then fix all discrepancies.

2026-03-280

audit-security

im9/inboil

Scan the codebase for security vulnerabilities. Check OWASP top 10, input validation, auth, crypto, and known BACKLOG security items.

2026-03-260

refactor

im9/inboil

Scan the project for refactoring opportunities, then fix them. No behavior/visual changes.

2026-03-240

name	commit
description	Generate a commit message and create the commit in one step.
allowed-tools	Bash(git diff ), Bash(git status ), Bash(git log ), Bash(git add ), Bash(git commit *)

Commit

Analyze current changes, generate a commit message, stage relevant files, and commit.

Process

Run git diff (unstaged) and git diff --cached (staged) to see all changes.
Run git status -u to see untracked files.
Run git log --oneline -5 to match the repository's commit style.
Analyze all changes and draft a commit message.
Stage relevant files (git add — prefer specific files over -A).
Create the commit.

Commit Message Format

First line: type: short summary (under 72 chars)
- Types: feat, fix, refactor, style, docs, chore
Blank line, then bullet-point details for non-trivial changes
End with Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
If changes span multiple concerns (e.g. a bug fix AND a feature), use multiple type: paragraphs in the body
Write in English (per CLAUDE.md conventions)
Pass the message via HEREDOC for proper formatting

Safety

Never stage files that may contain secrets (.env, credentials, etc.)
Never use git add -A — always add specific files
Never push to remote — only commit locally