Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

Começar

commit

Estrelas11

Forks2

Atualizado28 de março de 2026 às 18:39

Commit staged and unstaged changes with a clear commit message

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

pwittchen

pwittchen/aictl

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	commit
description	Commit staged and unstaged changes with a clear commit message
allowed-tools	Bash

Commit workflow

Run git status to see all changed and untracked files.
Run git diff to review both staged and unstaged changes.
Run git log --oneline -5 to see recent commit style.
Stage relevant files by name — avoid git add -A or git add ..
Write a commit message following the rules below and commit.
Run git status to verify success.

Commit message rules

NEVER add Co-Authored-By, Signed-off-by, or any AI attribution lines.
Small, trivial changes (typo fix, one-liner, rename) get a single short line — no body needed.
Larger changes get a short summary line followed by a blank line and a detailed body explaining what changed and why.
Summary line must be imperative mood, max 72 characters (e.g. "Add OpenAI provider support").
Body lines wrap at 72 characters.
Focus on why the change was made, not just what changed.
Do not repeat filenames or diffs in the message — describe intent.

Examples

Small change:

Fix typo in README

Larger change:

Add streaming support for Anthropic provider

Send requests with stream=true and read server-sent events
incrementally, printing tokens as they arrive. This gives immediate
feedback for long responses instead of waiting for the full completion.

Mais deste repositório

mesmo repositório

sync-models

pwittchen/aictl

Check each provider for newly released models, compare against the supported set, add any missing ones, and update the per-provider docs and website accordingly

2026-05-1511

update-docs

pwittchen/aictl

Update README.md, CLAUDE.md, the docs/ tree (ARCH.md, INSTALL.md, USAGE.md, CONFIG.md, PROVIDERS.md, TOOLS.md, EXTENSIONS.md, CODING_AGENT.md, SERVER.md), and the website (website/index.html, website/terminal.html, website/server.html, website/desktop.html) to match the current project state

2026-05-1511

write-code-snippet

pwittchen/aictl

Write a small, self-contained, locally executable code snippet — bash or python by default.

2026-04-2911

add-mcp-server

pwittchen/aictl

Connect a Model Context Protocol server to aictl by adding an entry to ~/.aictl/mcp.json. Walks the user through command, args, env, and timeout, then merges the new server into the existing config without disturbing other entries.

2026-04-2911

create-hook

pwittchen/aictl

Add a lifecycle hook to ~/.aictl/hooks.json. Walks the user through choosing the right event, matcher, command, and timeout, then merges the new entry into the existing config without disturbing other hooks.

2026-04-2811

review-code

pwittchen/aictl

Review staged/unstaged changes for correctness, security, and style.

2026-04-2111

name	commit
description	Commit staged and unstaged changes with a clear commit message
allowed-tools	Bash

Commit workflow

Run git status to see all changed and untracked files.
Run git diff to review both staged and unstaged changes.
Run git log --oneline -5 to see recent commit style.
Stage relevant files by name — avoid git add -A or git add ..
Write a commit message following the rules below and commit.
Run git status to verify success.

Commit message rules

NEVER add Co-Authored-By, Signed-off-by, or any AI attribution lines.
Small, trivial changes (typo fix, one-liner, rename) get a single short line — no body needed.
Larger changes get a short summary line followed by a blank line and a detailed body explaining what changed and why.
Summary line must be imperative mood, max 72 characters (e.g. "Add OpenAI provider support").
Body lines wrap at 72 characters.
Focus on why the change was made, not just what changed.
Do not repeat filenames or diffs in the message — describe intent.

Examples

Small change:

Fix typo in README

Larger change:

Add streaming support for Anthropic provider

Send requests with stream=true and read server-sent events
incrementally, printing tokens as they arrive. This gives immediate
feedback for long responses instead of waiting for the full completion.