Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

Commencer

git-commit

Étoiles0

Forks0

Mis à jour10 juin 2026 à 13:25

User when asked to commit changes in a Git repository.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

alexgorbatchev

alexgorbatchev/ai-registry

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

Explorateur de fichiers

3 fichiers

SKILL.md

readonly

name	git-commit
description	User when asked to commit changes in a Git repository.
author	alexgorbatchev

When requested to commit, analyze the user's intent to select the correct strategy:

1. Default: Commit Changed Files Only

If the user asks to commit, or when finalizing changes made during the session, always default to committing only the files that you have modified.

Reference: See commit-changed-files.md for detailed guidelines, message structure, and staging rules.
Goal: Protect files modified by other agents/collaborators in the same repository by only staging your own changes.

2. Explicit Override: Commit All Files

Only commit all files if the user explicitly asks to commit all files (e.g., "commit all", "commit everything").

Reference: See commit-all-files.md for rules on grouping and committing accumulated, unrelated changes.
Goal: Safely identify, group, and make individual commits for accumulated, uncommitted work in the repository.

Plus depuis ce dépôt

même dépôt

agent-browser

alexgorbatchev/ai-registry

Use agent-browser for browser automation against real rendered web pages or web apps. Trigger when tasks require navigation, element interaction, extracting rendered data, or taking screenshots. Do not use for static fetches, direct API calls, or non-browser work.

2026-07-150

firecrawl-cli

alexgorbatchev/ai-registry

Use when the user wants to scrape websites, crawl or map URLs, search the web, extract structured data from web pages, or run AI web agents using the Firecrawl API from the command line.

2026-07-150

skill-writer

alexgorbatchev/ai-registry

Create, revise, and validate effective skills. Use when adding a new skill or changing an existing skill's SKILL.md, bundled scripts, references, assets, scaffold templates, or validation tooling.

2026-06-250

typescript

alexgorbatchev/ai-registry

Must use any time a TypeScript file is read or written.

2026-06-240

bun

alexgorbatchev/ai-registry

Must use whenever Bun is used.

2026-06-170

opencode-sessions

alexgorbatchev/ai-registry

OpenCode session storage locations and inspection guidance. Use when asked where OpenCode stores session data, chat history, local databases, or repo-specific session metadata.

2026-06-170

name	git-commit
description	User when asked to commit changes in a Git repository.
author	alexgorbatchev

When requested to commit, analyze the user's intent to select the correct strategy:

1. Default: Commit Changed Files Only

If the user asks to commit, or when finalizing changes made during the session, always default to committing only the files that you have modified.

Reference: See commit-changed-files.md for detailed guidelines, message structure, and staging rules.
Goal: Protect files modified by other agents/collaborators in the same repository by only staging your own changes.

2. Explicit Override: Commit All Files

Only commit all files if the user explicitly asks to commit all files (e.g., "commit all", "commit everything").

Reference: See commit-all-files.md for rules on grouping and committing accumulated, unrelated changes.
Goal: Safely identify, group, and make individual commits for accumulated, uncommitted work in the repository.