Git Commit

What it does

The source centers the commit message on the actual staged change and the repository conventions. It distinguishes a request to create a commit from a request for message text alone, and treats unrelated edits as a reason to separate scope. This makes it a practical checkpoint between implementation and review, provided the agent has authorized local repository write access.

Best for

Developers who want consistent commit messages for a bounded change in an existing Git repository. It can help explain why a fix is needed and identify a breaking change, but repository-specific contribution rules remain authoritative.

Tradeoffs and requirements

Staging changes and creating a commit are real local mutations. Review the index, hooks, secret exposure and unrelated work before allowing them. Some source options require recent Git versions; check installed support rather than assuming a flag exists. A clean message does not prove tests passed or deployment succeeded.

Requires Git. The `--resolved` option of `git add` requires Git 2.56 or later.

Install from the source

First time installing a skill? Follow the walkthrough →

Inspect the pinned source snapshot and its supporting files first. The command selects this skill through the open-source skills CLI. Node.js and agent-specific setup may be required. Installation can download code. Catalog ingestion never executes skill instructions or install scripts.

npx skills add https://github.com/github/awesome-copilot/tree/61fa1fa8fcc63d6dbd2f07a75aeb8e214df5acfb/skills/git-commit --skill git-commit

Review pinned skill folder ↗ · CLI documentation ↗

After source review, use npx skills check and npx skills update to inspect and apply upstream updates. Re-check changed instructions before running them.

Safety & review signals

Static review only. This is not a security audit or a guarantee of safety.

SKILL.md text only; scripts, dependencies and runtime behavior not audited.

• Credential Reference — review the source context.
• Network Access — review the source context.
• Shell Or Package Install — review the source context.

Allowed tools declaration: shell(git:*). Runtime permissions and network behavior: Unknown.

AI Craft Pad Skill Score

87/100 · Metadata coverage 100% · Model 1.0

Scores summarize observable discovery signals. Popularity and repository activity apply to the whole repository. Unknown runtime safety earns no certification.

Documentation

100/100

100

Maintenance

100/100

100

License Clarity

100/100

100

Repository Health

100/100

100

Compatibility Evidence

80/100

80

Popularity

83/100

83

Originality

80/100

80

Static Safety

60/100

60

Suggested workflow

Read the project contribution rules, inspect working and staged diffs, choose one logical scope and review the exact staged file list. Create the requested commit only after the required checks. Keep push, publication, rebase and history modification as separately authorized operations.

How to judge the result

This is a source-based editorial assessment, not a runtime test of Git hooks or agent behavior. Inspect the final commit and parent diff, verify only intended files were included, and preserve the actual validation record. No execution result from another skill or task is inherited by this entry.