一键在 Manus 中运行任何 Skill

$pwd:

commit-all

Name: Commit All
Author: spacedriveapp

// 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.

在 Manus 中运行

$ git log --oneline --stat

stars:2,249

forks:342

updated:2026年4月9日 19:35

SKILL.md

readonly

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.

related-skills.json

同仓库

wiki-writing.md

from "spacedriveapp/spacebot"

Use when creating or substantially editing wiki pages. Covers language, tone, structure, page type selection, linking discipline, and what separates a useful wiki article from filler.

2026-04-082.2k

writing-guide.md

from "spacedriveapp/spacebot"

Use when writing or editing any Spacebot copy — README sections, docs, release notes, marketing text, design doc summaries. Covers voice, tone, patterns to avoid, and what good Spacebot writing sounds like.

2026-04-052.2k

prompt-review.md

from "spacedriveapp/spacebot"

This skill should be used when the user asks to "review the prompt", "audit the system prompt", "check prompt quality", "inspect what the LLM sees", "debug prompt issues", or "find prompt engineering problems". Pulls the live rendered prompt via the API, explains how it's composed, and reviews it for issues.

2026-03-212.2k

release-bump-changelog.md

from "spacedriveapp/spacebot"

Use this skill when preparing a release bump or updating release notes. It writes a launch-style release story from the actual change set, then runs `cargo bump` so the generated GitHub notes and the marketing copy land together in `CHANGELOG.md`.

2026-03-042.2k

async-state-safety.md

from "spacedriveapp/spacebot"

This skill should be used when the user asks to change "worker lifecycle", "cancellation", "retrigger behavior", "state machine", "delivery receipts", "timeouts", or "race conditions". Enforces explicit async/state invariants and targeted race-safe verification.

2026-02-262.2k

messaging-adapter-parity.md

from "spacedriveapp/spacebot"

This skill should be used when the user asks to change "Slack adapter", "Telegram adapter", "Discord adapter", "Webhook adapter", "status delivery", "message routing", or "delivery receipts". Enforces cross-adapter parity and explicit delivery semantics.

2026-02-262.2k

package.json

"author": "spacedriveapp"

"repository": "spacedriveapp/spacebot"

打开 GitHub 仓库查看创作者相关仓库

$ install --global

$ download --local

在 Manus 中运行

$ useful --forSOC

软件开发工程师计算机与数学类职业15-1252L4

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.

commit-all

Commit All

Goal

Workflow

Commit Message Rules

Hard Rules

同仓库更多 Skills

Commit All

Goal

Workflow

Commit Message Rules

Hard Rules

同仓库更多 Skills