git-workflow

Enforce commit message formatting, secret detection, and safe push behavior in Git workflows.

Updated Apr 11, 2023
One-click install
npx skills add https://github.com/salverius-tech/dotfiles --skill git-workflow-salverius-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/salverius-tech/dotfiles/tree/main/home/dot_claude/skills/git-workflow
Command: npx skills add https://github.com/salverius-tech/dotfiles --skill git-workflow-salverius-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures secure, standardized, and efficient Git operations by enforcing best practices for commits, pushes, and history management, preventing security breaches and maintaining code integrity.

Core Features & Use Cases

  • Security Scanning: Automatically detects and prevents commits containing secrets like API keys and tokens.
  • Commit Standardization: Enforces conventional commit message formats and logical commit grouping.
  • Safe Operations: Implements strict rules against dangerous commands like git filter-branch and force pushes.
  • Use Case: Before committing sensitive code changes, this Skill scans for any accidentally included API keys, prompts for a standardized commit message, and ensures the commit is atomic and well-described.

Quick Start

Activate the git-workflow skill before committing your changes.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I prevent committing API keys and secrets into my Git repository?

To prevent committing secrets, this Git workflow Skill automatically scans staged changes for API keys and tokens, blocking commits that contain sensitive data before they reach your repository history.

How do I enforce conventional commit message formatting in Git?

Enforcing conventional commit message formatting is handled by this Skill through strict rules that verify logical commit grouping and standardized message structure, rejecting commits that do not adhere to the specified format.

How do I block dangerous Git commands like force push and history rewriting?

Blocking dangerous Git commands is achieved by this Skill through strict prohibitions on destructive operations, preventing force pushes and commands like git filter-branch to maintain code integrity.

Does this Git workflow Skill integrate with pull request checks?

Yes, this Skill applies to all version control activities including pull request checks, enforcing security scanning, commit standardization, and safe operations across the entire Git workflow lifecycle.

What are the limitations of using automated Git workflow rules for version control?

Limitations include strict adherence to RFC 2119 for critical directives and enforced prohibitions on history rewriting, meaning developers cannot perform force pushes or use destructive commands when this Skill is active.