tool-git-github

Automate Git and GitHub workflows for branching, commits, and pull requests.

1|Updated Oct 5, 2025

Search Tags:#git #workflow #github #branching #code-review #pull-requests #conventional-commits

Ready to run

npx skills add https://github.com/simon-downes/agent-workspace --skill tool-git-github

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tool-git-github
Source: https://github.com/simon-downes/agent-workspace/tree/main/skills/tool-git-github
Command: npx skills add https://github.com/simon-downes/agent-workspace --skill tool-git-github

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git and GitHub workflows are error-prone and time-consuming without a standardized approach to branching, PRs, commits, and reviews.

Core Features & Use Cases

Standardized Git workflows: trunk-based or feature-branch strategies, branch naming, and syncing with remote.
GitHub PR operations: automated PR creation, review guidance, and merge conventions.
Commit hygiene and reviews: conventional commit guidance, code review prompts, and traceability.

Quick Start

Create a feature branch from main, push it to the remote, and open a pull request with a descriptive title and a concise body.

Frequently Asked Questions about tool-git-github

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

FAQPage Schema

How do I standardize Git workflows for feature branches and pull requests?▼

Standardizing Git workflows involves enforcing trunk-based development strategies, branch naming conventions, and structured pull request bodies. This approach automates version control tasks to reduce errors and streamline code reviews across software repositories.

What are conventional commits and how do they apply to GitHub pull requests?▼

Conventional commits are a standardized messaging format used to ensure commit hygiene and traceability. Applied to GitHub pull requests, they provide clear context for code reviews and automate the tracking of changes across development branches.

Can I use this to automate GitHub PR creation and code review guidance?▼

Yes, you can automate GitHub PR creation and generate code review guidance. It standardizes pull request titles and bodies, ensuring concise descriptions and consistent merge conventions across your software development workflow.

Does this approach support trunk-based development and branch syncing?▼

Yes, this approach supports trunk-based development by standardizing feature branch creation from main. It ensures proper branch naming conventions and handles syncing your local feature branches with the remote repository.

What is the best way to manage code reviews and PR approvals across repositories?▼

The best way to manage code reviews and PR approvals is by enforcing standardized PR bodies and merge conventions. This ensures consistent traceability and structured review guidance across multiple software development repositories.