skills.rest
ejoliet
ejolietCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

git-workflow

Enforce Conventional Commits, safe staging, and pre-push validation in Git workflows.

Updated Apr 16, 2026
Search Tags:#git#workflow#security#branching#worktree#pre-push#conventional-commits
One-click install
npx skills add https://github.com/ejoliet/claude-skills --skill git-workflow-ejoliet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/ejoliet/claude-skills/tree/main/git-workflow
Command: npx skills add https://github.com/ejoliet/claude-skills --skill git-workflow-ejoliet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes and hardens Git workflows to reduce human error, enforce conventions, and improve release discipline across teams.

Core Features & Use Cases

  • Conventional Commit formatting guidance and enforcement for subject, body, and footer.
  • Safe staging and targeted commits to avoid accidental changes or exposure of secrets.
  • Pre-push validation, branch strategy guidance, and worktree support for parallel development.
  • Use Case: When preparing a release or integrating a feature, apply consistent commits, checks, and release-ready branch setups.

Quick Start

Enforce the team's git workflow on the current repository by validating commits, staging changes safely, and preparing release branches.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I enforce conventional commits across my team's git workflow?▼

To enforce conventional commits, this Skill validates the subject, body, and footer of your commits against the standard format, ensuring consistent history and minimizing human error during staging.

What's the best way to prevent secrets from being committed to git?▼

Preventing secrets in git is handled through strict no-secret policies and safe staging validation, ensuring accidental exposure of sensitive data is blocked before changes are committed.

How does pre-push validation work for branch management?▼

Pre-push validation runs automated checks on your staged changes and branch strategy before remote transmission, ensuring release-ready branch setups and blocking non-compliant code from integration.

Can I use git worktree for parallel development with standardized workflows?▼

Git worktree is supported for parallel development, allowing you to manage multiple branches simultaneously while applying standardized commit formatting and pre-push validation across all active worktrees.

How do I prepare a release branch using standardized git workflows?▼

Release preparation applies consistent commit checks, safe staging, and branch strategy guidance to ensure your release branch is validated, secure, and free of unintended changes before deployment.

Why do I need safe staging for targeted commits?▼

Safe staging is needed to isolate targeted changes and avoid accidental commits, ensuring only verified modifications are applied while enforcing no-secret policies within every workflow operation.

Related Skills

Explore More Software Engineering Skills→
clawperatorclawperator
2

repo-setup

Configure local git hooks path and executable permissions for repository clones.

Official
Basic
vikisingh23vikisingh23
4

changelog

...

Community
Intermediate
yongwoonyongwoon
8

ywc-create-pr

Automate Git feature branch commits, security validation, and draft pull request creation.

Community
Advanced
Haohao-endHaohao-end
779

setup-pre-commit

Configure pre-commit hooks to run linting, formatting, and validation checks.

Community
Basic