skills.rest
brunoreinstein-cloud
brunoreinstein-cloudCOMMUNITY
Explore all skills by this author →
GitHub

commit

Create standardized Git commit messages following Conventional Commits in Portuguese.

Updated Aug 27, 2026
Search Tags:#git#commit#lint#version-control#conventional-commits#assistjur
One-click install
npx skills add https://github.com/brunoreinstein-cloud/chat-assitjur --skill commit-brunoreinstein-cloud
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/brunoreinstein-cloud/chat-assitjur/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/brunoreinstein-cloud/chat-assitjur --skill commit-brunoreinstein-cloud

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool standardizes commit messages according to AssistJur conventions (Conventional Commits in Portuguese), ensuring consistent project history and easier reviews.

Core Features & Use Cases

  • Enforces Conventional Commits structure in messages.
  • Guides scope and concise description in Portuguese.
  • Helps teams maintain a clean, searchable changelog through semantic commits.

Quick Start

Craft a conventional commit message that succinctly describes the change.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I create conventional commit messages in Portuguese for my Git repository?▼

Conventional commits in Portuguese standardize your Git history by enforcing a structured message format with an optional scope and strict description. This outputs a ready-to-use commit payload for consistent project tracking.

What is the best way to enforce semantic commit conventions across a software engineering team?▼

Enforcing semantic commit conventions is best achieved by automating structured commit message creation. This guarantees a clean, searchable changelog by applying strict Conventional Commits standards across your team's project history.

How do I structure a Git commit message with an optional scope and strict description?▼

Structuring a Git commit message requires applying a conventional format with a type, optional scope, and strict description. This generates a ready-to-use commit payload following the AssistJur conventions for consistent version control.

Does this conventional commit tool work for projects using Git and AssistJur conventions?▼

Yes, this tool is designed for software projects using Git and teams adopting Conventional Commits with AssistJur conventions. It enforces structured message formatting to ensure consistent project history and easier code reviews.

Why use Conventional Commits in Portuguese for version control history?▼

Using Conventional Commits in Portuguese standardizes version control history according to AssistJur conventions. It enforces a structured commit message format, ensuring a clean, searchable changelog and facilitating easier code reviews.

Related Skills

Explore More Software Engineering Skills→
d0whc3rd0whc3r
2

speckit-git-initialize

Initialize a Git repository and create an initial commit.

Community
Intermediate
xloxn69xloxn69
7

agileflow-commit-messages

Format git commit messages using the Conventional Commits specification.

Community
Basic
DGouronDGouron
41

commit

Enforce quality gates and conventional commit rules in Git workflows.

Community
Advanced
kirvinkirvin

commit

Stage Git changes and create conventional commit messages with preflight checks.

Community
Intermediate