skills.rest
scanady
scanadyCOMMUNITY
Explore all skills by this author →
GitHub

engineering-dev-git-commit

Executes the git inspect, stage, commit, and push cycle with conventional commit messages.

Updated Jan 28, 2026
Search Tags:#git#version control#commit#developer workflow#conventional commits#staging#push
One-click install
npx skills add https://github.com/scanady/nexus-skills --skill engineering-dev-git-commit-scanady
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: engineering-dev-git-commit
Source: https://github.com/scanady/nexus-skills/tree/main/skills/engineering-dev-git-commit
Command: npx skills add https://github.com/scanady/nexus-skills --skill engineering-dev-git-commit-scanady

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing clear commit messages and running the full commit-and-push cycle manually is repetitive and error-prone, often resulting in vague messages like "update" or "fix stuff" that hurt code history readability. ## Core Features & Use Cases - Diff Inspection and Analysis: Runs git status, git diff, and git diff --staged to understand changes before drafting any message. - Conventional Commit Messages: Generates tight messages in the type(scope): description format with subjects under 50 characters, imperative mood, and BREAKING CHANGE footers when needed. - Selective Staging and Safe Push: Stages only files belonging to one logical commit and pushes with git push -u origin <branch> on any platform. - Use Case: After finishing a bug fix across three files, ask the agent to commit and push; it inspects the diff, drafts "fix(api): null check user profile", stages the relevant files, commits, and pushes the branch. ## Quick Start Ask the agent to commit and push the current changes in this repository with a proper conventional commit message.

Frequently Asked Questions about engineering-dev-git-commit

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

FAQPage Schema
How do I write a good conventional commit message?▼

Use the format type(scope): short description with a subject under 50 characters in imperative mood and no trailing period. Pick the type from feat, fix, docs, style, refactor, test, chore, perf, or ci based on the change, for example feat(auth): add jwt login.

How to commit and push changes in git from the command line?▼

First inspect with git status and git diff, stage the relevant files with git add, commit with git commit -m "type(scope): desc", then push using git push -u origin <branch>. The -u flag sets the upstream on first push and is safe afterward.

Do these git commands work on Windows, macOS, and Linux?▼

Yes, all commands used are platform-agnostic and work on Linux, macOS, and Windows including PowerShell, Git Bash, and cmd. No bash-specific syntax is required.

How do I mark a breaking change in a commit message?▼

Add an exclamation mark after the type, such as feat(api)!: restructure response format, and include a BREAKING CHANGE: footer in the commit body explaining what changed and how consumers should update.

When should I not stage all files with git add -A?▼

Avoid staging everything when the working tree contains unrelated changes that belong in separate logical commits. Use git add -p or add specific files and directories so each commit stays focused and reviewable.

Related Skills

Explore More Software Engineering Skills→
kaosnyrbkaosnyrb
12

commit

Stage and commit Git changes with a diff-derived message.

Community
Intermediate
RonHoubenRonHouben
2

merge-pull-request

Merge approved GitHub pull requests via GitHub CLI after CI checks pass.

Community
Intermediate
owenlamontowenlamont
1

python-lint-format

Automate Python code linting and formatting with pre-commit hooks.

Community
Advanced
psmfdpsmfd

gitflow-expert

Provides read-only Git workflow guidance covering branching strategies, merge methods, and commit conventions.

Official
Intermediate