committing-changes

Enforce Git commit and branch workflows for the TileOPs repository.

168|55|Updated Jun 3, 2025
One-click install
npx skills add https://github.com/tile-ai/TileOPs --skill committing-changes-tile-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: committing-changes
Source: https://github.com/tile-ai/TileOPs/tree/main/.claude/skills/committing-changes
Command: npx skills add https://github.com/tile-ai/TileOPs --skill committing-changes-tile-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pre-commit, and includes scripts (resource) components.

What problem does it solve?

This Skill prevents accidental or nonconforming Git commits in the TileOPs repository by guiding branch creation, staging, commit formatting, and validations so that changes are clean, reviewable, and follow project conventions.

Core Features & Use Cases

  • Branch detection and creation: Detects if you're on main or a feature branch and creates a properly formatted feature branch when needed.
  • Targeted staging: Enforces staging of specific files only, avoiding accidental inclusion of unrelated changes.
  • Pre- and post-commit validation: Runs pre-commit hooks, checks branch name patterns, validates commit message format, and scans for large files before allowing a push.
  • Use Case: Use this Skill when preparing a single, well-formed commit for a new operator implementation or bugfix to ensure CI and repository standards are met.

Quick Start

Create a feature branch, stage only the files to change, run the pre-commit validation, commit with the repository template, and push the branch.

Frequently Asked Questions about committing-changes

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

FAQPage Schema
How do I create a feature branch and commit changes with proper Git workflow conventions?

Git commit validation checks branch naming patterns, commit message formats, and scans for large files using validation scripts before allowing a push. This ensures changes are clean, reviewable, and follow repository conventions.

Why does pre-commit fail when I try to push my Git changes?

Git commit validation checks branch naming patterns, commit message formats, and scans for large files using validation scripts before allowing a push. This ensures changes are clean, reviewable, and follow repository conventions.

What's the best way to stage specific files and avoid accidental changes in a Git commit?

The best way to stage specific files in Git is to use targeted staging, which enforces adding only the intended files and avoids accidental inclusion of unrelated changes. This ensures your commit remains focused and reviewable.

Do I need pre-commit installed to validate Git commits and branch workflows?

Yes, you need pre-commit installed to run the validation hooks that check branch naming patterns, validate commit message formats, and scan for large files. This dependency is required to enforce repository standards before pushing.

How do I prevent direct commits to main or master branch in Git?

To prevent direct commits to main or master in Git, use a workflow that detects your current branch and automatically creates a properly formatted feature branch. This enforces branching patterns and ensures all changes go through code review.