git-guidelines

Name: git-guidelines
Availability: InStock
Author: Joyan

Guide Git commits, PR descriptions, and remote actions with confirmation.

Updated Dec 26, 2025

Search Tags:#git #workflow #commit #code-quality #pull-request #gh-cli

Ready to run

npx skills add https://github.com/JoyanLabs/template-nestjs-dashboard-better_auth --skill git-guidelines-joyanlabs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-guidelines
Source: https://github.com/JoyanLabs/template-nestjs-dashboard-better_auth/tree/main/skills/git-guidelines
Command: npx skills add https://github.com/JoyanLabs/template-nestjs-dashboard-better_auth --skill git-guidelines-joyanlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Git guidelines and templates for commits, PR descriptions, and GitHub CLI workflows to ensure consistency and reduce miscommunication.

Core Features & Use Cases

Commit conventions: enforce standardized types, scopes, and messages.
PR descriptions: generate clear, actionable pull request bodies.
Remote-action safety: require explicit confirmation before commands that modify remote repos (e.g., git push, gh pr create).
CLI-guided workflows: detect gh availability and offer fallback manual steps when unavailable.

Quick Start

Follow the prompts to specify your Git task (commit, PR, or template generation), and I will provide a compliant message and the exact commands to execute.

Frequently Asked Questions about git-guidelines

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

FAQPage Schema

How do I write consistent git commit messages and PR descriptions?▼

To write consistent git commit messages and PR descriptions, you apply standardized conventions for types, scopes, and messages. This generates clear, actionable pull request bodies and enforces a uniform commit history across repositories.

What's the best way to manage remote git actions safely?▼

The best way to manage remote git actions safely is to require explicit confirmation before executing commands that modify remote repos. This prevents accidental pushes or pull request creations by pausing to verify each remote state modification.

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

You do not strictly need the GitHub CLI installed to automate pull request workflows. The system detects gh availability and offers fallback manual steps when the CLI is unavailable, ensuring workflows proceed without interruption.

How do I create a standardized pull request template?▼

To create a standardized pull request template, you specify your PR generation task and the system provides a compliant, actionable description body. This templating approach ensures clear communication and reduces miscommunication across multiple repositories.

Why should I use explicit commit conventions for my repository?▼

You should use explicit commit conventions for your repository to reduce miscommunication and ensure code quality. Standardized types and scopes make commit history readable, enabling clearer tracking of changes and more actionable pull request descriptions.