commit

Solid

Creates commits with Conventional Commits format (feat/fix/docs/refactor/test/chore), automatic scope detection, co-author attribution, and pre-commit hook compliance. Validates staged changes, generates descriptive messages focusing on the 'why', and prevents secrets or generated-only files from being committed. Use when committing changes or generating commit messages.

AI & Automation 188 stars 15 forks Updated today MIT

Install

View on GitHub

Quality Score: 86/100

Stars 20%
76
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Smart Commit Simple, validated commit creation. Run checks locally, no agents needed for standard commits. > **Note:** If `disableSkillShellExecution` is enabled (CC 2.1.91), the git repository check won't run. This skill requires a git repository. ## Quick Start ```bash /ork:commit /ork:commit fix typo in auth module ``` ## Argument Resolution ```python COMMIT_MSG = "$ARGUMENTS" # Optional commit message, e.g., "fix typo in auth module" # If provided, use as commit message. If empty, generate from staged changes. # $ARGUMENTS[0] is the first token (CC 2.1.59 indexed access) ``` ## STEP 0: Choose Commit Mode (AskUserQuestion — M118 #1465) Default is "new commit", but voice-flow needs explicit choice when amend / push / stash is wanted: ```python # Skip when a flag in the invocation makes the mode unambiguous: # /ork:commit --amend → skip, mode=amend # /ork:commit --push → skip, mode=new+push # /ork:commit --stash → skip, mode=stash-first # ORK_COMMIT_DEFAULT_MODE=new (or amend|push|stash) → skip, use env value # # Otherwise, ask: AskUserQuestion(questions=[{ "question": "How should this commit land?", "header": "Commit mode", "options": [ {"label": "New commit (default)", "description": "Create a new commit, leave HEAD intact"}, {"label": "Amend HEAD", "description": "Fold staged changes into the last commit (LOCAL ONLY — refuses if HEAD is published)"}, {"label": "New commit + push", "description": "Commit then `git push` (refuses on...

Details

Author
yonatangross
Repository
yonatangross/orchestkit
Created
5 months ago
Last Updated
today
Language
TypeScript
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

commit

Create a git commit following the Conventional Commits specification (conventionalcommits.org). Reads the diff, auto-infers scope from file paths, proposes type + scope + description + body, and shows the message for approval before committing. Supports optional push, language choice, Codex attribution, staging control, breaking-change marking, amend, and issue references. Global and project-agnostic. Trigger when the user says "commit", "make a commit", "commit my changes", "create a commit", "$commit", or "commit with conventional commits".

2 Updated 6 days ago
ada-ggf25
Code & Development Listed

commit

Generate a Conventional Commits message from the staged diff and create the commit after user confirmation. TRIGGER when the user says "commit these changes", "commit this", "generate a commit message", "stage and commit", "commit with CC", "write a commit message", "summarize my diff into a commit", "/nyann:commit". Do NOT trigger on "git commit" in an informational context or when the user is just asking what a commit message means. DISAMBIGUATION: if the user mentions BOTH branch creation AND committing in the same message (e.g. "start a branch and commit this", "new branch + commit"), route to the `new-branch` skill FIRST; `commit` will take over after the branch is created. When nothing is staged, guide the user to stage first rather than silently staging everything.

6 Updated 5 days ago
thettwe
AI & Automation Solid

commit

Creates Conventional Commits with pre-commit validation. Triggers: commit, conventional commit, git commit, message.

155 Updated 2 days ago
softspark