Generate a conventional commit message from the current Wox working tree diff.
npx skills add https://github.com/Wox-launcher/Wox --skill wox-commit
Please help me install this Agent Skill. Skill: wox-commit Source: https://github.com/Wox-launcher/Wox/tree/main/.agents/skills/wox-commit Command: npx skills add https://github.com/Wox-launcher/Wox --skill wox-commit
Writing consistent, well-scoped commit messages that cover every change in a working tree is tedious and error-prone, especially when a diff spans multiple unrelated behaviors. This Skill inspects the current Wox repository state and produces a copy-ready commit message without modifying the repository.
git status, staged and unstaged diffs, and untracked files to infer every distinct behavior change.type(scope): imperative summary format and matches the wording of nearby commits, omitting misleading narrow scopes when changes span unrelated areas.git commit.Ask the assistant to use $wox-commit to review your current Wox changes and write a commit message for them.
High-intent search queries and answers about installing and using this skill.
Invoke the Skill with $wox-commit and it inspects git status, staged and unstaged diffs, and untracked files to infer every behavior change. It returns one fenced block containing a subject line and body you can paste directly into a commit.
It uses the conventional `type(scope): imperative summary` format with types like feat, fix, refactor, docs, test, build, and chore. The scope is chosen from the narrowest accurate scope already used by nearby commits in the repository.
No. The Skill only reads the working tree and generates a message. It never stages, commits, amends, pushes, or otherwise modifies the repository, and it does not run tests or hooks.
Yes. It names each distinct behavior in the message, putting the dominant change in the subject and the others in the body, or naming peer features together. It avoids picking a misleading narrow scope when changes span unrelated areas.
The Skill still returns the standard fenced message block format, then adds a brief note after the block indicating that the diff is empty. It does not fabricate a message for nonexistent changes.
luigiinredReview staged changes, run linters and tests, and generate conventional commit messages.
vstorm-coManage git commits, branches, pull requests, and conflict resolution.
dylan-murrayReview Git staged changes for defects, security risks, and style issues.
learntocloudRun pre-commit checks, stage, commit, push, and monitor deployment.