Run any Skill in Manus with one click

commit

Stars29

Forks1

UpdatedJune 27, 2026 at 16:48

Create VCS commits for session changes. Use when the user wants to commit their work with well-structured, atomic commits.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

atomicinnovation

atomicinnovation/accelerator

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	commit
description	Create VCS commits for session changes. Use when the user wants to commit their work with well-structured, atomic commits.
argument-hint	[optional message or flags]
allowed-tools	["Bash(${CLAUDE_PLUGIN_ROOT}/scripts/*)"]

Commit Changes

!${CLAUDE_PLUGIN_ROOT}/scripts/vcs-status.sh !${CLAUDE_PLUGIN_ROOT}/scripts/vcs-log.sh !${CLAUDE_PLUGIN_ROOT}/scripts/config-read-context.sh !${CLAUDE_PLUGIN_ROOT}/scripts/config-read-skill-context.sh commit

Process:

Think about what changed:

Review the conversation history and understand what was accomplished
Review the VCS status and diff above to see what files changed
Consider whether changes should be one commit or multiple logical commits

Plan your commit(s):

Identify which files belong together
Draft clear, descriptive commit messages
Use imperative mood in commit messages
Focus on why the changes were made, not just what

Present your plan to the user:

List the files you plan to include in each commit
Show the commit message(s) you'll use
Use the AskUserQuestion tool with two options:
1. Yes, proceed — create [N] commit(s) with the staged changes
2. No, cancel — abort without committing

Execute upon confirmation:

Stage and commit the planned files with your planned messages
Use the VCS commands appropriate for this repository (refer to the session's VCS context for the correct commands)
Show recent commit history to confirm the result

Important:

NEVER add co-author information or Claude attribution
Commits should be authored solely by the user
Do not include any "Generated with Claude" messages
Do not add "Co-Authored-By" lines
Write commit messages as if the user wrote them
Use the VCS commands appropriate for this repository's version control system (refer to the session's VCS context for the correct commands)
When staging files, always add specific files by name — never bulk-add all changes at once

Remember:

You have the full context of what was done in this session
Group related changes together
Keep commits focused and atomic when possible
The user trusts your judgment - they asked you to commit

!${CLAUDE_PLUGIN_ROOT}/scripts/config-read-skill-instructions.sh commit

More from this repository

same repository

visualise

atomicinnovation/accelerator

Open the accelerator meta visualiser. Launches the companion-window server in the background and returns a URL. Subcommands stop and status manage the running server.

2026-07-1829

migrate

atomicinnovation/accelerator

Apply pending Accelerator meta-directory migrations to bring a repo into line with the latest plugin schema. Destructive by default but guarded — refuses to run on a dirty working tree and prints a one-line preview per pending migration before applying.

2026-07-1329

inventory-design

atomicinnovation/accelerator

Generate a structured design inventory for a frontend source — tokens, components, screens, and features — by crawling it with code analysis, live Playwright inspection, or both. Use when you need to capture a snapshot of a current or target design surface before running analyse-design-gaps. Produces a dated artifact directory with an inventory.md and screenshots/. Re-running for the same source-id supersedes the prior snapshot without losing it.

2026-07-1029

analyse-design-gaps

atomicinnovation/accelerator

Compare two design inventories produced by inventory-design and emit a structured gap artefact whose prose paragraphs satisfy the extract-work-items cue-phrase contract. Use after running inventory-design for both a current and target design surface. The resulting gap artefact under meta/design-gaps/ feeds directly into /accelerator:extract-work-items to produce actionable work items.

2026-07-1029

research-codebase

atomicinnovation/accelerator

Conduct comprehensive codebase research by spawning parallel subagents and synthesising findings into a research document. Use when the user needs to deeply understand a codebase area or answer technical questions.

2026-07-1029

configure

atomicinnovation/accelerator

View, create, or edit Accelerator plugin configuration. Manage document templates.

2026-07-1029

Commit Changes

Process:

Think about what changed:

Review the conversation history and understand what was accomplished

Review the VCS status and diff above to see what files changed

Consider whether changes should be one commit or multiple logical commits

Plan your commit(s):

Identify which files belong together

Draft clear, descriptive commit messages

Use imperative mood in commit messages

Focus on why the changes were made, not just what

Present your plan to the user:

List the files you plan to include in each commit

Show the commit message(s) you'll use

Use the AskUserQuestion tool with two options:

Yes, proceed — create [N] commit(s) with the staged changes
No, cancel — abort without committing

Execute upon confirmation:

Stage and commit the planned files with your planned messages

Use the VCS commands appropriate for this repository (refer to the session's VCS context for the correct commands)

Show recent commit history to confirm the result

Important:

NEVER add co-author information or Claude attribution

Commits should be authored solely by the user

Do not include any "Generated with Claude" messages

Do not add "Co-Authored-By" lines

Write commit messages as if the user wrote them

Use the VCS commands appropriate for this repository's version control system (refer to the session's VCS context for the correct commands)

When staging files, always add specific files by name — never bulk-add all changes at once

Remember:

You have the full context of what was done in this session

Group related changes together

Keep commits focused and atomic when possible

The user trusts your judgment - they asked you to commit

!${CLAUDE_PLUGIN_ROOT}/scripts/config-read-skill-instructions.sh commit