git-commit-pr

Name: git-commit-pr
Availability: InStock
Author: Sir-chawakorn

Stage code changes and generate Conventional Commits messages from git diffs.

9|3|Updated Jun 13, 2026

Search Tags:#automation #git #workflow #pull request #conventional commits #github

Ready to run

npx skills add https://github.com/Sir-chawakorn/sanook-cli --skill git-commit-pr-sir-chawakorn

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-commit-pr
Source: https://github.com/Sir-chawakorn/sanook-cli/tree/main/skills/git-commit-pr
Command: npx skills add https://github.com/Sir-chawakorn/sanook-cli --skill git-commit-pr-sir-chawakorn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the manual overhead of crafting standardized commit messages and the repetitive process of opening pull requests, ensuring your repository history remains clean and structured.

Core Features & Use Cases

Conventional Commits: Automatically generates structured commit messages based on actual code diffs.
Safety Checks: Scans for sensitive information like API keys or secrets before staging changes.
Automated PR Creation: Streamlines the creation of pull requests with pre-formatted summaries, change logs, and test plans using the GitHub CLI.

Quick Start

Ask the agent to commit your current changes and open a pull request with a summary of the work performed.

Frequently Asked Questions about git-commit-pr

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

FAQPage Schema

How do I automate conventional commits and pull request creation?▼

You can automate conventional commits and PR creation by using a skill that analyzes git diffs and repository logs to generate commit messages, then uses GitHub CLI to open pull requests with summaries and test plans.

What is the best way to generate conventional commit messages from git diffs?▼

Generating conventional commit messages from git diffs is best handled by analyzing your staged code changes alongside repository logs to automatically produce structured, standardized commit history entries.

Do I need GitHub CLI installed to automate pull request workflows?▼

Yes, you need GitHub CLI installed and authenticated in your local environment to automate pull request creation, as the workflow relies on it to generate summaries and test plans.

Can I scan for API keys and secrets before staging code changes?▼

Yes, you can scan for API keys and secrets before staging code changes. The workflow includes safety checks that detect sensitive information to prevent it from being committed to your repository.

How does automated pull request creation format summaries and test plans?▼

Automated pull request creation formats summaries and test plans by analyzing your committed git diffs and repository logs, then structuring the output into pre-formatted change logs via GitHub CLI.

Does this workflow require git and gh CLI to be authenticated locally?▼

Yes, this workflow requires both git and gh CLI to be installed and authenticated in your local environment to successfully stage changes, generate conventional commits, and open pull requests.