Agent Skills › spacedriveapp/spacebot › commit-all

commit-all

GitHub

用于将工作区所有未提交的更改分组提交。避免使用全量添加，而是按逻辑关联（如功能、配置）分离文件，生成多个描述清晰、顺序合理的独立提交，确保 Git 历史整洁且可追溯。

.agents/skills/commit-all/SKILL.md spacedriveapp/spacebot

Trigger Scenarios

用户要求 'commit all' 用户要求 'commit everything' 用户希望提交所有待处理的更改

Install

npx skills add spacedriveapp/spacebot --skill commit-all -g -y

More Options

Non-standard path

npx skills add https://github.com/spacedriveapp/spacebot/tree/main/.agents/skills/commit-all -g -y

Use without installing

npx skills use spacedriveapp/spacebot@commit-all

指定 Agent (Claude Code)

npx skills add spacedriveapp/spacebot --skill commit-all -a claude-code -g -y

安装 repo 全部 skill

npx skills add spacedriveapp/spacebot --all -g -y

预览 repo 内 skill

npx skills add spacedriveapp/spacebot --list

SKILL.md

Frontmatter

{
    "name": "commit-all",
    "description": "Use this skill when the user asks to \"commit all\", \"commit everything\", or wants all outstanding changes committed. Groups unrelated changes into separate, well-described commits instead of one catch-all commit."
}

Commit All

Goal

Commit every outstanding change in the working tree — but group unrelated changes into separate, informative commits so the git history stays useful.

Workflow

Survey all changes. Run git status and git diff (staged + unstaged) to see the full picture. Include untracked files.
Identify logical groups. Cluster files by the change they belong to. A "group" is a set of files that were modified for the same reason (e.g. a bug fix, a new feature, a config tweak, a dependency update). Use file paths, diff content, and your understanding of the codebase to decide.
Order commits. Infra/config/dependency changes first, then library/core changes, then feature/UI changes, then docs/polish.
For each group, create one commit:
- Stage only the files belonging to that group (git add <file> ...). Never use git add -A or git add ..
- Write a concise, informative commit message that describes what changed and why. Follow the repo's existing commit style (check git log --oneline -10).
- Do not lump unrelated changes together just because they're small.
Verify. After all commits, run git status to confirm the tree is clean. Run git log --oneline -n <N> (where N = number of commits created) to show the user what was committed.

Commit Message Rules

Keep the subject line under 72 characters.
Use imperative mood ("add", "fix", "update", not "added", "fixes").
If a change is trivial (whitespace, typo, formatting), it's fine to batch those into one commit labeled accordingly.
End every commit message with the Co-Authored-By trailer.

Hard Rules

Never combine unrelated changes in one commit.
Never skip or discard changes — everything gets committed.
Never use git add -A or git add ..
Do not push. Only commit locally.
Do not commit files that look like they contain secrets (.env, credentials, tokens). Warn the user about those instead.