commit-and-report

Commit and push local Git changes and report commit messages to GitHub Issues.

1|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/dobachi/claude-skills-marketplace --skill commit-and-report
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-and-report
Source: https://github.com/dobachi/claude-skills-marketplace/tree/main/plugins/commit-and-report/skills/commit-and-report
Command: npx skills add https://github.com/dobachi/claude-skills-marketplace --skill commit-and-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the repetitive workflow of committing changes, pushing them to a remote repository, and then manually updating the corresponding GitHub Issue with what was done.

Core Features & Use Cases

  • One-step commit + push: stages the current directory, creates a commit using the provided message, and pushes to the configured remote.
  • Issue progress reporting: when an issue number is included, it automatically posts a GitHub issue comment containing the commit message (and can close the issue when work is complete).
  • Use Case: When fixing a bug tied to a specific GitHub Issue, you can commit and push your changes, then immediately notify the issue with the commit details so stakeholders can track progress.

Quick Start

Run /commit-and-report "feat: implement custom commands" 123 to commit your changes, push them, and report the commit message to GitHub Issue 123.

Frequently Asked Questions about commit-and-report

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

FAQPage Schema
How do I automatically push Git changes and comment on a GitHub issue at the same time?

You can automatically push Git changes and comment on a GitHub issue by running a single command that stages, commits, pushes to remote, and posts the commit message using GitHub CLI.

What is the best way to update a GitHub issue with my commit message after pushing code?

The best way to update a GitHub issue is using an automated workflow that pushes your local Git changes and posts the exact commit message directly to the issue thread via GitHub CLI.

Do I need the GitHub CLI installed to report commit progress to issues?

Yes, you need the GitHub CLI installed because the progress reporting feature relies on the 'gh issue comment' command to post commit messages to the specified GitHub issue.

Can I use this to stage, commit, and push local Git changes in one step?

Yes, you can stage, commit, and push local Git changes in one step by providing a commit message, which automates the standard git status, add, commit, and push workflow.

How do I close a GitHub issue automatically when committing a fix?

You can close a GitHub issue automatically by including the issue number when running your commit and push command, which reports the progress and can close the issue upon completion.

What happens if I commit and push without providing a GitHub issue number?

If you commit and push without a GitHub issue number, the workflow completes the local Git changes and remote push normally, but skips the automated GitHub issue comment posting.