skills.rest
emergent-company
emergent-companyOFFICIAL
Explore all skills by this author →
GitHub

commit

Stage, commit, and push Git changes with conventional messages.

1|Updated Feb 6, 2026
Search Tags:#git#version control#commit#push#gitignore#code staging
One-click install
npx skills add https://github.com/emergent-company/emergent.memory --skill commit-emergent-company
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/emergent-company/emergent.memory/tree/main/.opencode/skills/commit
Command: npx skills add https://github.com/emergent-company/emergent.memory --skill commit-emergent-company

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of saving your code changes by automating staging, committing with descriptive messages, and pushing to your remote repository.

Core Features & Use Cases

  • Intelligent Staging: Commits only relevant files for the current feature by default, or all files if specified.
  • Automated Commit Messages: Generates conventional commit messages based on code changes.
  • .gitignore Management: Optionally updates .gitignore for newly detected ignored files.
  • Use Case: After completing a new feature, use this Skill to quickly and safely commit your work without manually typing git commands or crafting commit messages.

Quick Start

Use the commit skill to stage, commit, and push the current feature changes.

Frequently Asked Questions about commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate git commit and push for code changes?▼

You can automate git commit and push by using a skill that stages modified files, generates conventional commit messages based on code changes, and pushes to your remote repository automatically.

How do I generate conventional commit messages automatically from code changes?▼

Generating conventional commit messages from code changes involves analyzing the staged diff to create descriptive messages. This skill automates that analysis to produce standardized commit messages without manual input.

Can I stage only feature-specific files for a git commit instead of all changes?▼

Yes, you can stage only feature-specific files for a git commit. By default, this skill intelligently commits only relevant files for the current feature, or stages all files if explicitly specified.

How do I update .gitignore for newly detected files before committing?▼

Updating .gitignore for newly detected files before committing involves identifying untracked files that should be excluded. This skill optionally updates .gitignore automatically to manage newly detected ignored files.

Do I need Git CLI installed to use automated git staging and pushing?▼

Yes, you need Git CLI installed to use automated git staging and pushing. This skill requires Git CLI and adherence to Git best practices to ensure safe and efficient version control operations.

What is the best way to handle version control for feature-specific code changes?▼

The best way to handle version control for feature-specific code changes is to automate staging, commit message generation, and pushing. This ensures only relevant files are committed with descriptive conventional messages.

Related Skills

Explore More Software Engineering Skills→
okbest2024okbest2024

memory-git-sync

Automate OpenClaw workspace backups to a remote Git repository.

Community
Intermediate
JacobPEvansJacobPEvans
3

rebase-pr

Rebase pull requests onto main with signed commits and GitHub API checks.

Community
Advanced
jchildreejchildree
1

safe-push

Validate git pushes with pre-push checks for large files and test failures.

Community
Intermediate
tobihagemanntobihagemann
399

stage

Stage specific files or code hunks for a Git commit.

Community
Basic