skills.rest
dEitY719
dEitY719COMMUNITY
Explore all skills by this author →
GitHub

gh:commit

Create styled git commits with optional GitHub issue links.

Updated May 31, 2025
Search Tags:#automation#git#workflow#commit#shell#version-control#issue-linking
One-click install
npx skills add https://github.com/dEitY719/dotfiles --skill gh-commit-deity719
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gh:commit
Source: https://github.com/dEitY719/dotfiles/tree/main/claude/skills/gh-commit
Command: npx skills add https://github.com/dEitY719/dotfiles --skill gh-commit-deity719

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of staging relevant changes and creating a new git commit that follows the repository's existing style, including optional linking to a GitHub issue.

Core Features & Use Cases

  • Inspect the working tree to determine changes before committing.
  • Resolve an explicit issue number from arguments or recent chat messages and attach it as Refs/Closes footer when available.
  • Draft a commit message that matches the project style and uses a heredoc to ensure proper formatting.
  • Stage only the files needed for the commit, avoiding accidental secrets or unrelated changes.
  • Apply standard Git hooks and safety checks; never amend or push.
  • Use the help command to display usage details from references/help.md.

Quick Start

Run the gh-commit command after making changes to automatically stage relevant edits and create a properly formatted commit with optional issue linkage.

Frequently Asked Questions about gh:commit

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

FAQPage Schema
How do I create a git commit that automatically links to a GitHub issue?▼

You can automate git commits with issue linking by inspecting the working tree, resolving the issue number from arguments or chat, drafting a compliant message, staging files, and committing using a heredoc format.

What is the best way to stage only relevant files for a version control commit?▼

Staging only relevant files for a version control commit requires inspecting the working tree to isolate specific changes, preventing accidental secrets or unrelated modifications from entering the commit history.

Can I use shell automation to draft git commit messages that match my project style?▼

You can use shell automation to draft git commit messages matching project style by leveraging a heredoc to maintain formatting, ensuring the generated message adheres to existing repository conventions.

Does this git commit workflow run standard Git hooks and safety checks?▼

This git commit workflow applies standard Git hooks and safety checks during commit creation, explicitly avoiding amending existing commits or pushing to remote repositories.

How do I resolve a GitHub issue number for a commit without specifying it manually?▼

Resolving a GitHub issue number without manual input involves checking recent chat messages for context, then attaching it as a Refs or Closes footer in the commit message when available.

What are the limitations of automating git commits with issue linking?▼

Limitations of automating git commits with issue linking include the inability to amend existing commits or push to remote repositories, restricting its workflow to local repository work only.

Related Skills

Explore More Software Engineering Skills→
ian-pascoeian-pascoe
1

git-commit

Generate conventional git commit messages and stage related file changes.

Community
Advanced
n0ann0an
103

commit-to-git

Automates Git commits with confirmation and project-style messages.

Community
Intermediate
yunseo-kimyunseo-kim
1

issue-analysis

Gather and analyze issue context, attachments, media, and effort estimates.

Community
Advanced
irudikirudik
6

commit

Automate Git commit, pull request, and merge cycles via GitHub CLI.

Community
Intermediate