skills.rest
Glorktelligence
GlorktelligenceCOMMUNITY
Explore all skills by this author →
GitHub

Git Workflow

Commit and push code changes to a remote repository using Conventional Commits.

Updated Mar 11, 2026
Search Tags:#git#workflow#version control#commit#conventional commits#push
One-click install
npx skills add https://github.com/Glorktelligence/Bastion --skill git-workflow-glorktelligence
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Git Workflow
Source: https://github.com/Glorktelligence/Bastion/tree/main/.claude/skills/git-workflow
Command: npx skills add https://github.com/Glorktelligence/Bastion --skill git-workflow-glorktelligence

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that all completed work is properly version controlled, committed, and pushed to the remote repository, maintaining a clear and auditable history of changes.

Core Features & Use Cases

  • Standardized Committing: Enforces the use of Conventional Commits for clear and consistent commit messages.
  • Push Enforcement: Ensures code is pushed to the main branch after committing.
  • Failure Handling: Provides a clear process for handling Git push failures.
  • Protocol Versioning: Guides on how to handle breaking changes in the protocol.
  • Use Case: After implementing a new feature, you need to commit your changes with a descriptive message and push them to the main branch for review.

Quick Start

Commit your changes using a message that follows the Conventional Commits standard and push them to the main branch.

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 for my Git workflow?▼

This Git workflow Skill standardizes commit messages during the staging process, enforcing Conventional Commits to ensure clear and consistent version control history before pushing to the remote repository.

What is the best way to handle push failures when committing code to a remote repository?▼

This Git workflow provides a structured process to resolve push failures and protocol version bumps, ensuring your committed code changes are successfully pushed to the remote repository's main branch.

Does this Git workflow support handling protocol version bumps for breaking changes?▼

Yes, this Git workflow supports handling protocol version bumps by guiding you through the process of managing breaking changes in the protocol during your standard version control and push operations.

When do I need to use a structured workflow for committing and pushing code changes?▼

You need a structured workflow for committing and pushing code changes when working in software development teams that require disciplined version control practices and an auditable history of changes on the main branch.

Can I use this Conventional Commits workflow for pushing code changes to any branch?▼

This Conventional Commits workflow enforces pushing code changes specifically to the main branch, ensuring all completed work is properly version controlled and maintained in a clear, auditable history.

Related Skills

Explore More Software Engineering Skills→
consultantvisionconsultantvision

git-sync

Automate Git commits and push local changes to GitHub.

Community
Intermediate
cogpycogpy

prepare-pr

Rebase GitHub pull requests onto main, apply review fixes, and run automated gates.

Official
Advanced
TopengDevTopengDev

preflight

Run local linting, testing, and building checks before pushing code.

Community
Advanced
TashanGKDTashanGKD
5

git-commit-conventions

Normalize and validate Git commits and pull requests against conventional commit standards.

Official
Advanced