code-commit

Enforce pre-commit validation and standardized commit messages for FOUNDATION projects.

19|3|Updated Jul 19, 2024
One-click install
npx skills add https://github.com/danielterra/FOUNDATION --skill code-commit-danielterra
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-commit
Source: https://github.com/danielterra/FOUNDATION/tree/main/.claude/skills/code-commit
Command: npx skills add https://github.com/danielterra/FOUNDATION --skill code-commit-danielterra

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps ensure consistent commit messages and pre-commit validations for FOUNDATION projects, reducing mistakes and enforcing project conventions.

Core Features & Use Cases

  • Pre-commit validation: enforce structure and checks before commits.
  • Conventional commit guidance: standardizes messages and prefixes per project conventions, with Portuguese note where applicable.
  • Project-specific conventions: tailors rules to FOUNDATION's workflow and tooling.

Quick Start

Commit your changes with a clean, compliant message using the project's conventions.

Frequently Asked Questions about code-commit

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

FAQPage Schema
How do I enforce conventional commits for a project with specific Portuguese conventions?

This skill standardizes commit messages by validating formats, prefixes, and scopes against project conventions before git commits are finalized. It ensures deterministic pre-commit workflow compliance locally.

How do pre-commit hooks validate code, docs, and config changes?

Pre-commit hooks validate code, docs, and config changes by enforcing structural checks and project-specific rules before a commit is accepted. This process scopes changes across repositories to maintain project standards consistently.

Can I use this to enforce project standards across multiple repositories?

Yes, this skill enforces project standards across repositories by applying consistent pre-commit validation and conventional commit rules. It tailors checks to specific project workflows to maintain consistent commit metadata.

What is the best way to standardize git commit messages locally?

Standardizing git commit messages locally is best achieved by applying deterministic pre-commit validation to enforce conventional formats. This approach intercepts non-compliant messages before they enter the repository history.

Does this pre-commit validation require any external dependencies?

No external dependencies are required to run this pre-commit validation. The skill operates independently to enforce conventional commit formats and project-specific rules locally without needing additional installed packages.