在 Manus 中运行任何 Skill
一键导入
一键导入
一键在 Manus 中运行任何 Skill
开始使用git-commit
星标3
分支0
更新时间2026年7月10日 00:38
Create a git commit
安装
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
SKILL.md
readonly
相关职业SOC
基于 SOC 职业分类
菜单
Create a git commit
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Backlog-scale orchestration on top of /workflow — drives PM items through refine → plan → implement → review → local-merge via role-specialized sub-agents dispatched in parallel waves, each item isolated in its own git worktree. Bare /swarm summarizes state; /swarm <goal> runs the orchestrator; /swarm:setup sets up the charter and .agent-tools/ umbrella; /swarm:continue resumes a paused run.
Capture durable knowledge from any engineering work — debugging solutions, refactors, features, design decisions, reusable patterns — and maintain memory quality so each unit of work compounds the next
Principal workflow entry — resolve portfolio mode (swarm resume/handoff or unit state machine), drive work without inventing path; hard-stop when path is not established
Initialize and maintain planning root (.agent-tools/planning preferred), conventions (tracks, gates, integration), runs ledger scaffold, and shared memory under .agent-tools/memory/ (AGENTS.md memory-link) for the workflow family.
Parent skill for the workflow family — principal session entry is /workflow:continue (also bare /workflow). Horizon mapping, brainstorm, refine, plan, execute, review, audit, compound. Vertical-slice and deliverable-partition modes.
Detect gaps in the canonical skill corpus, propose targeted improvements, validate changes, and present for review. Inventories src/** skill trees; optional run-ledger seeds for process IP gaps.
| name | git:commit |
| user-invocable | true |
| allowed-tools | Bash(git add:*), Bash(git status:*), Bash(git commit:*), Bash(git diff:*), Bash(git branch:*), Bash(git log:*) |
| description | Create a git commit |
| argument-hint | [optional context about which changes to commit] |
NEVER use git -C <path> in any git command. The session is already active in the correct working directory. Always use plain git commands (e.g., git status, git add, git commit). This rule is absolute and has no exceptions. Violating this rule will produce incorrect results.
$ARGUMENTS
You MUST consider user input before proceeding, if not empty. The user may provide additional context about the outstanding changes, or may indicate which specific changes should be included.
If the user does not provide any input, commit all pending changes.
$ARGUMENTSgit statusgit diff HEADgit branch --show-currentgit log --oneline -10Based on the above changes, create a single git commit.
You have the capability to call multiple tools in a single response. Stage and create the commit using a single message. Do not use any other tools or do anything else. Do not send any other text or messages besides these tool calls.
Always follow Conventional Commits standard when formatting the commit message, and include a high-quality description without being overly verbose.
[A-Z]+-[0-9]+, e.g., PRJ-1470)type(scope): description ISSUE-KEYCloses ISSUE-KEY