Create Conventional Commits messages from session context and git diffs.
npx skills add https://github.com/david-nossebro/agent-commons --skill commit-david-nossebro
Please help me install this Agent Skill. Skill: commit Source: https://github.com/david-nossebro/agent-commons/tree/main/shared/skills/commit Command: npx skills add https://github.com/david-nossebro/agent-commons --skill commit-david-nossebro
It solves the problem of turning an active coding session into a clean, accurate git commit by inspecting what actually changed, choosing a conventional commit message, and committing safely.
git status --short and relevant diffs so the message matches the code.git add -A and creates a commit unless a real blocker or no-changes condition applies; reports the resulting commit header and summary.Ask the AI to commit the current work with a best-practice Conventional Commits message after reviewing the session context and the repo diffs.
High-intent search queries and answers about installing and using this skill.
To generate a conventional commit message from a git diff, the workflow analyzes repository changes and session context to produce an imperative commit header with appropriate type and scope. It inspects the actual file diffs to ensure the message accurately reflects the staged updates.
Yes, you can automatically stage all files and create a git commit in one step. The workflow executes git add -A to stage every update, analyzes the changes, generates a matching conventional commit message, and commits everything unless a real blocker or empty repository state prevents it.
The best way to write git commit messages that match your code changes is to inspect the repository state using git status and diff outputs. Reviewing the actual diffs alongside session context ensures the generated conventional commit message accurately represents the modified code.
Yes, automated commit generation works without manual staging beforehand. The workflow handles staging automatically by running git add -A across all updated files, inspecting the resulting diffs, and generating a conventional commit message before finalizing the git commit.
You should avoid automated conventional commits when a real blocker exists in your repository or when no changes are present. The workflow safely aborts the commit process if it detects an empty staging area or encounters a blocking condition during the diff review.
devturcoCreate a single git commit with a conventional-commits message.
bswrundquistCommit staged changes using conventional commits and push them to the remote repository.
channingwaltonGenerate conventional commit messages from staged git diffs.
biwakonbuStage changes and generate descriptive Git commit messages automatically.