crew-commit

Automate git commits with pre-flight checks, submodule awareness, and PR creation.

17.5k|1.6k|Updated Dec 16, 2025
One-click install
npx skills add https://github.com/gastownhall/gastown --skill crew-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crew-commit
Source: https://github.com/gastownhall/gastown/tree/main/.claude/skills/crew-commit
Command: npx skills add https://github.com/gastownhall/gastown --skill crew-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Canonical commit workflow for Gas Town crew members to ensure safe, reviewable changes.

Core Features & Use Cases

  • Pre-flight checks and origin sync
  • Branch creation and feature naming conventions
  • gt commit usage to set agent identity
  • Push to feature branch and PR creation
  • Guardrails to avoid committing to main and ensure code-review

Quick Start

Run /crew-commit to begin the canonical crew commit workflow for your changes.

Frequently Asked Questions about crew-commit

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

FAQPage Schema
How do I automate a git commit workflow with branch creation and pull requests?

To automate a git commit workflow, this Skill performs pre-flight checks, enforces branch naming conventions, pushes feature branches, and creates pull requests. It prevents direct commits to main and sets agent identity using gt commit.

How can I prevent commits directly to the main branch during development?

To prevent commits to the main branch, this Skill enforces built-in guardrails that block direct commits to main. It ensures all changes are pushed to a properly named feature branch for code review before merging.

Does this commit workflow handle git submodules during the sync process?

Yes, this commit workflow handles git submodules. It includes submodule awareness during pre-flight checks and origin sync to ensure repository dependencies are correctly updated before creating a pull request.

What is the best way to enforce branch naming conventions for feature branches?

The best way to enforce branch naming conventions is using this Skill's automated workflow. It validates and applies standardized feature branch names before pushing commits, ensuring consistent repository history and reviewable changes.

Can I use this pull request creation workflow for my daily development cycles?

Yes, you can use this pull request creation workflow for daily development cycles. It is specifically designed to automate canonical commit processes, sync with the origin, and manage feature branch updates safely.

Why does this git commit workflow use gt commit instead of standard git commands?

This git commit workflow uses gt commit to explicitly set agent identity for the commit author. This ensures automated changes are properly attributed and distinguishable from manual human commits during code review.