gormes-git

Commit dirty Gormes changes into coherent commits and push to origin development.

9|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/TrebuchetDynamics/gormes-agent --skill gormes-git
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gormes-git
Source: https://github.com/TrebuchetDynamics/gormes-agent/tree/main/development-skills/gormes-git
Command: npx skills add https://github.com/TrebuchetDynamics/gormes-agent --skill gormes-git

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Commit all dirty Gormes changes on the existing development branch, split the changes into coherent commits, validate the branch state, and push to origin development.

Core Features & Use Cases

  • Single-branch workflow on development with safety constraints.
  • Automatic, coherent commit separation by scope, preserving history.
  • Validation gates that prevent editing main and destructive actions; non-destructive workflows.
  • Pushes to origin development only when explicitly allowed by user.

Quick Start

Use gormes-git to inspect the dirty development worktree, reconcile generated surfaces, validate readiness, and push to origin development.

Frequently Asked Questions about gormes-git

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

FAQPage Schema
How do I automatically split dirty development branch changes into coherent git commits?

To split dirty development branch changes into coherent git commits, this Skill automates commit separation by scope. It inspects your dirty worktree, groups changes logically, and preserves history without destructive actions.

How do I safely push changes to origin development without risking the main branch?

To safely push changes to origin development, this Skill enforces validation gates that prevent editing main and destructive actions. It pushes only when explicitly allowed and uses non-interactive commands with timeouts.

What is the best way to automate a single-branch git workflow with safety constraints?

Automating a single-branch git workflow with safety constraints involves enforcing development branch rules and running non-destructive validation checks. This Skill reconciles generated surfaces and validates readiness before pushing.

Does this git automation workflow support non-interactive commands with explicit timeouts?

Yes, this git automation workflow supports non-interactive commands with explicit timeouts. It uses non-destructive commands to commit, split, and push development work cleanly without requiring user interaction during processing.

Can I use this tool to validate my development branch state before pushing to origin?

Yes, you can use this tool to validate your development branch state before pushing to origin. It reconciles generated surfaces and checks readiness to ensure the worktree is safe and coherent for pushing.

Why should I use an automated git workflow that prevents destructive actions on the main branch?

Using an automated git workflow that prevents destructive actions protects your main branch from accidental edits. This Skill enforces validation gates and single-branch constraints, ensuring non-destructive history preservation.