Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

Começar

git-commit

Estrelas14

Forks1

Atualizado13 de abril de 2026 às 03:06

Create a git commit using the message format below

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

doitian

doitian/dotfiles-public

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Programadores de computadorInformática e Matemática·SOC 15-1251

Desenvolvedores de softwareSOC 15-1252

SKILL.md

readonly

name	git-commit
description	Create a git commit using the message format below
disable-model-invocation	true

Create a git commit using the message format below.

Commit Message

Analyze outputs of following commands to generate the commit message:

git status --short (change overview)
git diff --staged (primary input). If the diff lacks sufficient context to understand intent, examine the full file.
git branch --show-current (ticket/feature context)
git log --oneline -n 5 --no-merges (subject style reference).

Message Format

<subject>

<body>

<further paragraphs>

Rules

Summarize the nature of the changes as <subject> (eg. new feature, enhancement to an existing feature, bug fix, refactoring, test, docs, etc.).
- Ensure the subject accurately reflects the changes and their purpose (i.e. "add" means a wholly new feature, "update" means an enhancement to an existing feature, "fix" means a bug fix, etc.).
- Subject is lowercase, no period at the end.
- Follow this repository's commit subject style by checking the output git log --oneline -n 5 --no-merges.
- Keep the subject within 72 characters
Draft a concise (1-2 sentences) <body> that focuses on the "why" rather than the "what".
- Body must use proper punctuation and capitalization like normal paragraphs.
Add <further paragraphs> if necessary. Bullet points are OK.
Wrap body and further paragraphs at 72 characters.

Attribution

When user asks to commit with AI attribution, include an Assisted-by tag in the following format:

Assisted-by: AGENT_NAME:MODEL_VERSION [TOOL1] [TOOL2]

Where:

AGENT_NAME is the name of the AI tool or framework
MODEL_VERSION is the specific model version used
[TOOL1] [TOOL2] are optional specialized analysis tools used (e.g., coccinelle, sparse, smatch, clang-tidy)

Basic development tools (git, gcc, make, editors) should not be listed.

Example:

Assisted-by: Claude:claude-3-opus coccinelle sparse

Mais deste repositório

mesmo repositório

jrnl

doitian/dotfiles-public

Capture notes into your daily journal using the jrnl CLI

2026-07-2214

create-google-task

doitian/dotfiles-public

Create a Google Task via the IFTTT JSON webhook

2026-07-2214

split-commit

doitian/dotfiles-public

Split working tree changes into up to five atomic commits, each with a message generated using the git-commit skill

2026-03-2514

bun-shell-src

doitian/dotfiles-public

Use Bun's shell API ($ from "bun") when writing or editing scripts that run shell commands in src/. Use when adding or changing subprocess/shell usage under src/, or when the user asks for shell execution in this project. Prefer Bun Shell over child_process or execSync.

2026-02-2414

polish

doitian/dotfiles-public

Polish text by refining clarity, coherence, and conciseness

2026-02-0514

crates-trusted-publishing

doitian/dotfiles-public

Add GitHub Actions workflow for publishing Rust crates using trusted publishing (OIDC). Use when setting up automated crate publishing, configuring crates.io trusted publishing, or when the user mentions crate publishing workflow.

2026-02-0214

name	git-commit
description	Create a git commit using the message format below
disable-model-invocation	true

Create a git commit using the message format below.

Commit Message

Analyze outputs of following commands to generate the commit message:

git status --short (change overview)
git diff --staged (primary input). If the diff lacks sufficient context to understand intent, examine the full file.
git branch --show-current (ticket/feature context)
git log --oneline -n 5 --no-merges (subject style reference).

Message Format

<subject>

<body>

<further paragraphs>

Rules

Summarize the nature of the changes as <subject> (eg. new feature, enhancement to an existing feature, bug fix, refactoring, test, docs, etc.).
- Ensure the subject accurately reflects the changes and their purpose (i.e. "add" means a wholly new feature, "update" means an enhancement to an existing feature, "fix" means a bug fix, etc.).
- Subject is lowercase, no period at the end.
- Follow this repository's commit subject style by checking the output git log --oneline -n 5 --no-merges.
- Keep the subject within 72 characters
Draft a concise (1-2 sentences) <body> that focuses on the "why" rather than the "what".
- Body must use proper punctuation and capitalization like normal paragraphs.
Add <further paragraphs> if necessary. Bullet points are OK.
Wrap body and further paragraphs at 72 characters.

Attribution

When user asks to commit with AI attribution, include an Assisted-by tag in the following format:

Assisted-by: AGENT_NAME:MODEL_VERSION [TOOL1] [TOOL2]

Where:

AGENT_NAME is the name of the AI tool or framework
MODEL_VERSION is the specific model version used
[TOOL1] [TOOL2] are optional specialized analysis tools used (e.g., coccinelle, sparse, smatch, clang-tidy)

Basic development tools (git, gcc, make, editors) should not be listed.

Example:

Assisted-by: Claude:claude-3-opus coccinelle sparse