git-standards

Name: git-standards
Availability: InStock
Author: joncrangle

Enforce Conventional Commits formatting and safety checks before commits and pushes.

8|Updated Mar 28, 2024

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

Ready to run

npx skills add https://github.com/joncrangle/.dotfiles --skill git-standards

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-standards
Source: https://github.com/joncrangle/.dotfiles/tree/main/dot_config/opencode/skills/git-standards
Command: npx skills add https://github.com/joncrangle/.dotfiles --skill git-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures safe, conventional git workflows by enforcing commit standards and safety reviews during development.

Core Features & Use Cases

Safety checks before commits and pushes using a formal protocol to detect secrets, large files, and build artifacts.
Conventions: enforce Conventional Commits formatting and provide a structured PR workflow.
Use Case: A developer on a feature branch runs this skill to ensure the next commit follows the conventional format and passes safety checks before creating a PR.

Quick Start

Validate a commit with the conventional format and run a safety check before pushing.

Frequently Asked Questions about git-standards

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

FAQPage Schema

How do I enforce conventional commits format in my git workflow?▼

Conventional commits are enforced by validating commit messages against the standard format before finalizing local commits or pull requests. This ensures uniform history across feature branches by rejecting messages that fail the structural protocol.

Can I run safety checks to prevent staging sensitive files before a git push?▼

Safety checks scan staged files to detect secrets, large files, and build artifacts before a push. The protocol validates actions using a dedicated tool to ensure sensitive files are not committed into the repository history.

What is the best way to validate a feature branch before creating a pull request?▼

Validating a feature branch requires running safety checks for sensitive files and enforcing conventional commit formatting. This structured PR workflow ensures code review standards are met before the branch is submitted.

Does this git workflow validation work for local commits as well as pull requests?▼

Git workflow validation applies across local commits, feature branches, and pull requests. It enforces message conventions and safety protocols uniformly at each stage to maintain repository history integrity.