skills.rest
plocher
plocherCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

git-workflow

Enforce iterative pre-commit validation and semantic commit messages for the jBOM repository.

3|Updated Dec 14, 2025
Search Tags:#automation#git#workflow#version control#semantic commits#pre-commit
One-click install
npx skills add https://github.com/plocher/jBOM --skill git-workflow-plocher
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/plocher/jBOM/tree/main/.agents/skills/git-workflow
Command: npx skills add https://github.com/plocher/jBOM --skill git-workflow-plocher

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates common git errors and repository inconsistencies by enforcing a strict, iterative pre-commit pattern and standardized commit messaging.

Core Features & Use Cases

  • Iterative Pre-commit Enforcement: Ensures code quality by requiring a specific loop of staging, linting, and re-staging before commits.
  • Semantic Commit Standardization: Provides a clear framework for conventional commits to automate versioning and changelog generation.
  • Branch Management: Defines clear rules for feature branching and post-merge cleanup to keep the repository history clean and navigable.

Quick Start

Use the git-workflow skill to guide you through the process of staging your changes, running the pre-commit hooks, and crafting a compliant semantic commit message.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I enforce a pre-commit validation loop for git staging and linting?▼

To enforce pre-commit validation, you must follow an iterative loop of staging changes, running linting hooks, and re-staging before finalizing the commit to ensure code quality.

What is a semantic commit message format for automated versioning?▼

A semantic commit message uses conventional commit types to provide a clear framework that automates versioning and generates changelogs for the repository.

How do I manage feature branching and post-merge cleanup in a git workflow?▼

Managing feature branching requires creating dedicated branches for development and performing post-merge cleanup to keep the repository history clean and navigable.

Do I need mandatory co-author attribution for my git commits?▼

Yes, this git workflow requires adherence to a mandatory co-author attribution policy for all commits within the repository to maintain accurate contribution tracking.

Why does my pre-commit hook fail when staging code changes?▼

Pre-commit hooks fail during staging to enforce iterative validation, requiring you to fix linting errors and re-stage your code before proceeding with the commit.

When do I need conventional commit types for my version control process?▼

You need conventional commit types during version control when you want to standardize commit messaging to automate versioning and changelog generation.

Related Skills

Explore More Software Engineering Skills→
0xjc65eth0xjc65eth
4

git-ops

Standardize Git commits, branching, pre-merge checks, and deployments for CYPHER V3.

Community
Intermediate
MayaDispelerMayaDispeler
3

git-workflow

Enforce git commit message formats, branch naming, and pull request guidelines.

Community
Advanced
miounet11miounet11

Git Smart Commit

Generate conventional commit messages from staged Git changes.

Community
Intermediate
imbue-aiimbue-ai
213

restack

Merge parent branch commits into child branches in a git stack.

Official
Advanced