name	commit
description	Create a well-structured git commit from staged or unstaged changes
user-invocable	true
trigger-condition	When the user asks to commit changes, create a commit, or save their work.
allowed-tools	["bash"]
required-context	["current git status","intended files for the commit","commit message focus"]
examples	["commit a staged bug fix","atomic commit before opening a pull request","save work-in-progress"]
verification-checklist	["git status --short shows only intended files","git log -1 shows the commit","no unrelated user changes included"]
progressive-disclosure	Inspect git status and the current diff first; only stage files that belong to the same logical change.

Create a git commit with normal non-interactive shell git commands:

Use bash to inspect git status --short, git diff, git diff --cached when staged files exist, and git log --oneline -5.
Identify exactly which files belong in the commit. Do not include unrelated user work.
Stage only intended files with explicit paths, for example git add src/file.ts tests/file_test.ts. Never use git add ., git add -A, root/current-directory pathspecs, wildcards, pathspec magic, or sensitive credential paths.
If unrelated files are already staged, unstage them with explicit paths, for example git restore --staged path/to/file.
Draft a concise commit message focusing on the "why".
Prefer one short shell transaction for tightly coupled staging and committing, for example git add path/to/file && git commit -m "message", after you have inspected the diff. This keeps the shared Git index window small when multiple sessions use the same repo.
Run git status --short after the commit to verify the result.
Do not push unless the user explicitly asked for a remote write.
Preserve existing Co-authored-by trailers, including trailers written by other tools. WUU adds its own trailer through the Git execution layer when attribution is enabled; never change author or committer Git configuration to add attribution.

Never update git config, skip hooks (--no-verify, --no-gpg-sign, etc.), amend, force push, run destructive git commands (reset --hard, clean -f, broad checkout/restore), or use interactive/editor-driven git flows unless the user explicitly requested that exact action and the runtime permits it. If a requested commit would require staging a sensitive path, stop and ask for explicit secret handling.

Más de este repositorio

mismo repositorio

browser

blueberrycongee/wuu

嵌入式浏览器自动化：在后台的隐藏网页宿主里导航、观察并操作网页。Use when a task must open, read, or act on a web page and no safer interface or connector can complete it.

2026-07-1712

skill-creator

blueberrycongee/wuu

Guide for creating effective skills. Use when the user wants to create a new skill or improve an existing one — a reusable instruction package that extends Wuu with specialized knowledge, workflows, or tool integrations.

2026-07-1212

cua-mac

blueberrycongee/wuu

Observe and control native macOS apps through Accessibility, ScreenCaptureKit, and native input. Use when a task requires interacting with a Mac app that has no safer CLI, API, or dedicated connector.

2026-07-1112

long-running-goal

blueberrycongee/wuu

Run durable multi-phase work without relying on one context window.

2026-07-0912

electron-debug

blueberrycongee/wuu

Debug Electron desktop issues across renderer, preload, main process, and Go app-server.

2026-07-0712

release-check

blueberrycongee/wuu

Run final release gates before publishing or handing off a build.

2026-07-0712

name	commit
description	Create a well-structured git commit from staged or unstaged changes
user-invocable	true
trigger-condition	When the user asks to commit changes, create a commit, or save their work.
allowed-tools	["bash"]
required-context	["current git status","intended files for the commit","commit message focus"]
examples	["commit a staged bug fix","atomic commit before opening a pull request","save work-in-progress"]
verification-checklist	["git status --short shows only intended files","git log -1 shows the commit","no unrelated user changes included"]
progressive-disclosure	Inspect git status and the current diff first; only stage files that belong to the same logical change.

Create a git commit with normal non-interactive shell git commands:

Use bash to inspect git status --short, git diff, git diff --cached when staged files exist, and git log --oneline -5.
Identify exactly which files belong in the commit. Do not include unrelated user work.
Stage only intended files with explicit paths, for example git add src/file.ts tests/file_test.ts. Never use git add ., git add -A, root/current-directory pathspecs, wildcards, pathspec magic, or sensitive credential paths.
If unrelated files are already staged, unstage them with explicit paths, for example git restore --staged path/to/file.
Draft a concise commit message focusing on the "why".
Prefer one short shell transaction for tightly coupled staging and committing, for example git add path/to/file && git commit -m "message", after you have inspected the diff. This keeps the shared Git index window small when multiple sessions use the same repo.
Run git status --short after the commit to verify the result.
Do not push unless the user explicitly asked for a remote write.
Preserve existing Co-authored-by trailers, including trailers written by other tools. WUU adds its own trailer through the Git execution layer when attribution is enabled; never change author or committer Git configuration to add attribution.