git-workflows

Standardize git workflows with explicit permission gates for risky operations.

Updated Nov 26, 2025
One-click install
npx skills add https://github.com/Aias/dotfiles --skill git-workflows-aias
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workflows
Source: https://github.com/Aias/dotfiles/tree/main/agents/skills/git-workflows
Command: npx skills add https://github.com/Aias/dotfiles --skill git-workflows-aias

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Standardizes git operations with explicit permission gates and guidelines to prevent unsafe commits, pushes, or resets.

Core Features & Use Cases

  • Permissioned commits and pushes: enforce explicit user approval for risky actions.
  • PR and merge workflows: guidance for merging, rebasing, conflict resolution, and PR prose.
  • Conductor context awareness: reads /pr-guidelines and /conductor for workspace-aligned rules.

Quick Start

Request explicit permission before performing high-risk git actions and refer to /git-workflows guidelines for routine operations.

Frequently Asked Questions about git-workflows

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

FAQPage Schema
How do I prevent unsafe git merges and pushes in my workflow?

You can prevent unsafe git merges and pushes by applying explicit permission gates that require user consent before executing high-risk operations like commits, pushes, or resets.

What is the best way to standardize git workflows for rebase and conflict resolution?

Standardizing git workflows for rebase and conflict resolution involves enforcing explicit permission gating and reading workspace-aligned rules from /conductor and /pr-guidelines directories to guide operations.

Do I need gh integration to manage PR guidelines?

Yes, you need gh integration for PR management to handle pull request prose, merges, and rebases while ensuring all risky actions receive explicit user consent.

Can I enforce explicit permissions for git stash and fetch operations?

Yes, you can enforce explicit permissions for git stash and fetch operations by applying permission gating across routine git actions to prevent unsafe execution.

Why does my git workflow require explicit user consent before a push?

Your git workflow requires explicit user consent before a push to prevent unsafe commits and enforce standardized permission gates across all high-risk branch operations.