Stages only task-relevant files and creates conventional git commits.
npx skills add https://github.com/wesbragagt/nixos-config --skill commit-wesbragagt
Please help me install this Agent Skill. Skill: commit Source: https://github.com/wesbragagt/nixos-config/tree/main/home/skills/commit Command: npx skills add https://github.com/wesbragagt/nixos-config --skill commit-wesbragagt
git add -A, ensuring each commit contains only the changes relevant to the current task. ## Core Features & Use Cases - Selective Staging: Reviews git status and diffs, then stages only files tied to the current task, with git add -p support for partial-file staging. - Conventional Commit Messages: Generates concise conventional commit messages (feat, fix, chore, refactor, docs, test, style, perf) under 72 characters in imperative mood. - Safety Guardrails: Surfaces leftover unstaged files, refuses empty commits, and verifies the git author is the user rather than an AI identity. - Use Case: After finishing a bug fix while other unrelated edits exist in the working tree, ask for a commit and only the fix-related files are staged and committed with a proper message. ## Quick Start Ask the assistant to commit the changes related to your current task with an optional commit message.High-intent search queries and answers about installing and using this skill.
Run git status to list changes, then stage specific files by name with git add <file1> <file2>. For partial changes within one file, use git add -p to stage individual hunks interactively before committing.
Use the format type(scope): summary, with types like feat, fix, chore, refactor, docs, test, style, or perf. Keep it lowercase, imperative, under 72 characters, and avoid vague words like updates or changes.
Blanket staging pulls unrelated edits, config drift, and auto-generated files into one commit, polluting history and making reviews and reverts harder. Staging files by name keeps each commit focused on a single task.
Yes, git add -p <file> opens an interactive prompt letting you stage individual hunks within a file. This is useful when one file contains both task-related and unrelated changes.
Confirm staged content with git diff --cached --stat, review remaining unstaged files via git status, and verify git config user.name and user.email are set to your identity rather than an AI or placeholder author.
m-de-graaffCreates isolated git worktrees with baseline test verification before starting feature work.
VYRE-StudiosCommit staged changes, push the branch, and open a pull request via GitHub CLI.
erfanzarAutomate pre-commit code review with static checks, linting, and auto-fixes.
cstrahanAutomate programmatic interactive rebases for git history cleanup and commit hygiene.