git-workflow

Enforce safe Git operations with pre-push checks and scoped commits.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/cmtkdot/arc --skill git-workflow-cmtkdot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/cmtkdot/arc/tree/main/skills/git-workflow
Command: npx skills add https://github.com/cmtkdot/arc --skill git-workflow-cmtkdot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Arc teams often rely on unsafe Git practices that can lead to destructive changes, broken histories, and untraceable commits. This skill enforces a consistent safety framework across all tiers and execution modes, providing guardrails for Git commands, pushes, and branch management.

Core Features & Use Cases

  • Enforces no destructive resets by default and blocks force-pushes to protected branches.
  • Validates pre-push checks (tests, lint, typecheck, build) and ensures commits are scoped to a single bead or task.
  • Standardizes branch naming (arc/<tier>/<description>) to improve traceability in collaborative projects.
  • Keeps specification artifacts in sync with code changes and ensures clean post-execution cleanup.

Quick Start

Start a Git operation session in Arc and follow the safety rails to complete your task.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I prevent destructive git force-pushes in team projects?

Git workflow safety rules block force-pushes to protected branches and prevent destructive resets by default. This framework enforces guardrails for git commands to avoid broken histories and untraceable commits in collaborative environments.

What's the best way to standardize branch naming for traceability?

Standardizing branch naming requires the arc/<tier>/<description> format to improve traceability in collaborative projects. This structure ensures branches clearly map to specific tasks and execution tiers across the team workflow.

How do I enforce pre-push checks for tests, lint, and typecheck?

Pre-push checks for tests, lint, typecheck, and build are validated automatically before completing a git push. This ensures code quality by verifying scoped commits and preventing broken changes from reaching shared branches.

Can I scope git commits to a single task to avoid mixing changes?

Scoping git commits to a single bead or task is enforced during your session to prevent mixing unrelated changes. This keeps specification artifacts in sync with code changes and maintains a clean, traceable project history.

Does this git workflow framework work across all execution modes in Arc?

The git workflow framework applies across all tiers and execution modes within Arc. It provides consistent safety guardrails for commits, pushes, rebases, and branch handling regardless of how your session is configured.

Why do my git rebases result in broken histories in collaborative projects?

Broken histories during rebases often occur from unsafe git practices lacking standardized guardrails. Enforcing pre-push checks, scoped commits, and no destructive resets prevents these issues and maintains a clean post-execution cleanup.