claude-import-git-workflow

Applies branch model and safety procedures for git pushes, cherry-picks, and rebases.

Updated Aug 25, 2017
One-click install
npx skills add https://github.com/loki495/dotfiles --skill claude-import-git-workflow-loki495
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: claude-import-git-workflow
Source: https://github.com/loki495/dotfiles/tree/main/ai/codex-skills/claude-import-git-workflow
Command: npx skills add https://github.com/loki495/dotfiles --skill claude-import-git-workflow-loki495

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Non-trivial git operations like force-pushes, rebases, and history rewrites carry a real risk of losing work or disrupting shared branches. This Skill enforces a consistent branch model and safety checklist before those operations run. ## Core Features & Use Cases - Branch Model Enforcement: Applies Andres's personal branching conventions to everyday git work. - Safety Gate for Risky Operations: Requires reading the full git-workflow reference before pushes, cherry-picks, rebases, and history surgery. - Explicit Permission Boundaries: Never grants permission to push, force-push, rewrite shared history, or discard work on its own. - Use Case: Before rebasing a feature branch onto an updated main, the Skill loads the underlying git-workflow rules so the rebase follows the established safety procedure instead of improvising. ## Quick Start Ask the assistant to prepare a rebase of your feature branch and have it follow the git-workflow safety procedures before running anything.

Frequently Asked Questions about claude-import-git-workflow

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

FAQPage Schema
How do I safely rebase a git branch without losing work?▼

Follow the branch model and safety procedures this Skill loads from the git-workflow reference before any rebase. It requires reading the full workflow rules first and never discards work or rewrites shared history without explicit permission.

What safety checks should run before a git force-push?▼

This Skill treats force-push as a restricted operation that it never authorizes by itself. It directs the assistant to read the complete git-workflow rules covering pushes and history surgery before proceeding.

Can this Skill push or rewrite git history automatically?▼

No. The Skill explicitly states it never grants permission to push, force-push, rewrite shared history, or discard work. Those actions always require separate explicit user approval.

When should I use a git workflow safety skill?▼

Use it before non-trivial git operations such as cherry-picks, rebases, and history surgery where mistakes can destroy commits or disrupt collaborators. Routine reads like status or log do not need it.

Does this Skill work without the referenced git-workflow file?▼

No. It depends on reading ~/dotfiles/ai/skills/git-workflow/SKILL.md completely, so that file must exist at the expected path for the procedures to load.