Run any Skill in Manus with one click

commit

Stars114

Forks32

UpdatedMarch 29, 2026 at 11:28

Create a git commit with a good message. Use when the user says "commit", "save changes", "commit this", or asks to create a commit after making code changes.

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

SeifBenayed

SeifBenayed/cloclo

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 a git commit with a good message. Use when the user says "commit", "save changes", "commit this", or asks to create a commit after making code changes.
allowed-tools	Bash, Read, Grep, Glob

Git Commit

Review all staged changes and create a well-crafted commit message.

Steps

Run git status to see staged and unstaged changes
Run git diff --cached to review staged changes in detail
If nothing is staged, run git diff and suggest what to stage based on the changes
Run git log --oneline -5 to see recent commit message style in the repo
Draft a concise commit message following conventional commits format:
- feat: — new feature
- fix: — bug fix
- refactor: — code restructuring without behavior change
- docs: — documentation changes
- test: — adding or updating tests
- chore: — build, tooling, config changes
Focus the message on why not what — the diff shows what changed
Keep the first line under 72 characters
Add a body paragraph if the change is non-trivial
Create the commit

Do NOT push unless explicitly asked. Do NOT use --no-verify or skip hooks.

$ARGUMENTS

More from this repository

same repository

debug

SeifBenayed/cloclo

Troubleshoot and debug issues. Use when the user reports an error, a test failure, unexpected behavior, or asks to investigate why something isn't working.

2026-03-29114

docx

SeifBenayed/cloclo

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.

2026-03-29114

file-reading

SeifBenayed/cloclo

Use this skill when a file has been uploaded but its content is NOT in your context — only its path at /mnt/user-data/uploads/ is listed in an uploaded_files block. This skill is a router: it tells you which tool to use for each file type (pdf, docx, xlsx, csv, json, images, archives, ebooks) so you read the right amount the right way instead of blindly running cat on a binary. Triggers: any mention of /mnt/user-data/uploads/, an uploaded_files section, a file_path tag, or a user asking about an uploaded file you have not yet read. Do NOT use this skill if the file content is already visible in your context inside a documents block — you already have it.

2026-03-29114

pdf-reading

SeifBenayed/cloclo

Use this skill when you need to read, inspect, or extract content from PDF files — especially when file content is NOT in your context and you need to read it from disk. Covers content inventory, text extraction, page rasterization for visual inspection, embedded image/attachment/table/form-field extraction, and choosing the right reading strategy for different document types (text-heavy, scanned, slide-decks, forms, data-heavy). Do NOT use this skill for PDF creation, form filling, merging, splitting, watermarking, or encryption — use the pdf skill instead.

2026-03-29114

pdf

SeifBenayed/cloclo

Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.

2026-03-29114

pptx

SeifBenayed/cloclo

Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.

2026-03-29114

name	commit
description	Create a git commit with a good message. Use when the user says "commit", "save changes", "commit this", or asks to create a commit after making code changes.
allowed-tools	Bash, Read, Grep, Glob

Git Commit

Review all staged changes and create a well-crafted commit message.

Steps

Run git status to see staged and unstaged changes
Run git diff --cached to review staged changes in detail
If nothing is staged, run git diff and suggest what to stage based on the changes
Run git log --oneline -5 to see recent commit message style in the repo
Draft a concise commit message following conventional commits format:
- feat: — new feature
- fix: — bug fix
- refactor: — code restructuring without behavior change
- docs: — documentation changes
- test: — adding or updating tests
- chore: — build, tooling, config changes
Focus the message on why not what — the diff shows what changed
Keep the first line under 72 characters
Add a body paragraph if the change is non-trivial
Create the commit

Do NOT push unless explicitly asked. Do NOT use --no-verify or skip hooks.

$ARGUMENTS