git-commit-rules

Enforces pre-staging diff inspection, atomic staging, and Conventional Commits formatting in git workflows.

Updated Aug 13, 2026
One-click install
npx skills add https://github.com/Martino17x/Sentinel-Invest --skill git-commit-rules-martino17x
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit-rules
Source: https://github.com/Martino17x/Sentinel-Invest/tree/main/.agents/skills/git-commit-rules
Command: npx skills add https://github.com/Martino17x/Sentinel-Invest --skill git-commit-rules-martino17x

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often commit accidental files, encoding errors, or messy bulk changes because staging and commit messages lack enforced discipline. This Skill defines mandatory rules for inspecting diffs, staging files granularly, and writing standardized commit messages in the Equarys repository. ## Core Features & Use Cases - Mandatory Pre-Staging Inspection: Requires running git status and git diff before any staging to catch temp files, mojibake, stray console.log statements, and unwanted formatting changes. - Atomic Granular Staging: Prohibits blind git add . or git add -A, requiring explicit file selection and logically grouped commits. - Conventional Commits Enforcement: Standardizes messages as <type>(<scope>): <description> with allowed types (feat, fix, refactor, style, test, docs, chore) and module scopes like promotions, pos, or auth. - AI Attribution Ban: Forbids Co-Authored-By AI trailers or watermarks in commits and code. - Use Case: After finishing a bugfix touching the catalog module, stage only the two affected files and commit with fix(catalog): correct price rounding on discount items. ## Quick Start Apply the git commit rules to review my current working tree, stage only the files for this feature, and write a compliant Conventional Commits message.

Frequently Asked Questions about git-commit-rules

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

FAQPage Schema
When should I commit during a development cycle?▼

Make small, cohesive commits for each specific change or fix rather than batching unrelated work. At the end of a full SDD (Spec-Driven Development) phase, create a final closing commit for that phase.