skills.rest
Andresch2
Andresch2COMMUNITY
Explore all skills by this author →
GitHub

commit

Stage relevant changes and create Git commits and pull requests via GitHub CLI.

Updated Feb 13, 2026
Search Tags:#git#version control#pull request#workflow automation#commit message#release process#change staging
One-click install
npx skills add https://github.com/Andresch2/Workflows --skill commit-andresch2
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/Andresch2/Workflows/tree/main/ai-specs/skills/commit
Command: npx skills add https://github.com/Andresch2/Workflows --skill commit-andresch2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you turn scattered local changes into a clean, reviewable commit and a well-scoped pull request that matches repository standards.

Core Features & Use Cases

  • Feature-scoped staging and commits: When you provide ticket IDs or feature labels, it stages only the relevant changes and leaves everything else unstaged.
  • Single comprehensive commit for general updates: When no arguments are provided, it stages and commits all relevant changes together, reducing fragmentation.
  • Commit-message quality and traceability: It produces descriptive English commit messages and PR text designed for clarity and review.

Use case: You have multiple modified files after working on SCRUM-123 and want a PR that includes only that ticket’s changes with a single, well-described commit.

Quick Start

Use it by instructing: "Commit the SCRUM-123 changes and open a pull request."

Frequently Asked Questions about commit

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

FAQPage Schema
How do I create a git pull request for specific ticket changes only?▼

To create a git pull request for specific ticket changes, you provide the ticket identifier to stage only matching files, generate a descriptive commit message, and open the PR via GitHub CLI.

What is the best way to automate staging feature-scoped git commits?▼

Automating feature-scoped git commits involves inspecting the working tree, matching modified files to provided feature labels, and staging only those relevant changes to ensure a focused and reviewable pull request.

How do I group all local modifications into a single comprehensive git commit?▼

To group all local modifications into a single comprehensive git commit, run the process without specific ticket arguments to stage all relevant changes together and generate one descriptive commit message.

Do I need GitHub CLI installed to automate opening pull requests from my local branch?▼

Yes, you need GitHub CLI installed to automate opening pull requests, as the workflow relies on it to push the local branch and create or update the PR directly from your terminal environment.

Can I leave unrelated working tree changes unstaged while committing a specific feature?▼

Yes, when you provide a specific ticket identifier or feature label, the process stages only those relevant changes and leaves everything else in your working tree completely unstaged.

Why use a single descriptive commit instead of fragmented commits for pull requests?▼

Using a single descriptive commit instead of fragmented commits reduces repository noise, improves change traceability for release workflows, and ensures the pull request meets repository-standard messaging for faster review.

Related Skills

Explore More Software Engineering Skills→
ahandselahandsel
1

git-pull-main

Synchronizes local Git feature branches with the remote main branch.

Community
Intermediate
JacobPEvansJacobPEvans
3

sync-main

Fetch remote main updates and merge them into the current branch.

Community
Intermediate
oxieoxie

staging-deployment-phase

Automate staging deployment with auto-merge for merged pull requests.

Community
Intermediate
mhattingpetemhattingpete
657

git-pushing

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

Community
Basic