commit
Commit stages files based on scope, intent, or both—parsing file paths, folders, and free-text descriptions to guide commit messages. Supports amending the last commit and integrates with sequenced workflows where the caller owns the final commit step.
Commit stages and commits files with flexible scope and free-text intent parsing for git workflows.
AI-generated summary based on this skill's SKILL.md
Install
benoror/obsidianos_work/commit · repository language: JavaScript
git clone https://github.com/benoror/obsidianos_work
cp -r obsidianos_work/.agents/skills/commit ~/.claude/skills/commitnpx skillfed install benoror/obsidianos_work/commitFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How does commit stage and commit files with flexible scope?
Commit stages files based on scope, intent, or both—parsing file paths, folders, and free-text descriptions to guide commit messages. You can specify exact files, entire directories, or provide a natural language description, and commit will infer the related changes and generate an appropriate message.
Can I amend the last commit with commit?
Yes. Commit supports amending the last commit safely with optional new scope or message. You can modify the previous commit's content or description without creating a new commit entry.
What does commit do with free-text intent parsing?
Commit parses free-text descriptions to infer related file changes and automatically generate commit messages. Rather than manually listing files, you describe what changed in natural language, and commit interprets your intent to stage and commit the relevant modifications.
Can commit handle specific files or folders?
Commit can commit specific files or folders with automatic message generation. Provide a file path or directory name, and commit will stage those changes and create an appropriate commit message based on the scope you've identified.
Does commit integrate with sequenced workflows?
Commit integrates with sequenced workflows for deferred multi-step commits. In such workflows, commit prepares and stages your changes while you retain control over the final commit step, enabling complex multi-stage operations.
What license does commit use?
Commit is released under the MIT license, allowing free use, modification, and distribution in both open-source and commercial projects.
SKILL.md
rendered from the published skill — quoted content, verbatim
Commit
Usage
| Command | What it does |
|---|---|
/commit |
Commit staged files; if none staged, infer related changes |
/commit <file> |
Scope to a specific file's changes |
/commit <folder>/ |
Scope to a folder's changes |
/commit <description> |
Infer scope from free-text intent |
/commit <scope> <description> |
Scope + explicit intent |
/commit amend |
Amend the last commit (re-use message) |
/commit amend <scope/description> |
Amend with additional scope or new message |
| (sequence mode) | Deferred — sub-skills skip, caller commits once at the end |
Argument Parsing
Parse the raw argument string into scope, intent, and flags:
- Amend flag: If the first word is
amend, set amend mode and strip it. The remainder is parsed normally. - Scope (file or folder): Any token that matches a real path in the repo (file or directory) — whether provided via
@-reference or plain text. Multiple scopes are allowed. - Intent (free-text
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 1 file
.agents/skills/commit/SKILL.md