Standardize git commits with conventional types and Terrae's frontmatter rules.
npx skills add https://github.com/alamenai/terrae --skill commit-alamenai
Please help me install this Agent Skill. Skill: commit Source: https://github.com/alamenai/terrae/tree/main/.claude/skills/commit Command: npx skills add https://github.com/alamenai/terrae --skill commit-alamenai
Creates consistent, well-structured git commits that align with Terrae's conventions, improving history readability and collaboration.
Review the changes, stage the appropriate files, and commit using the conventional commit format (type(scope): description).
High-intent search queries and answers about installing and using this skill.
To standardize git commit messages, apply conventional commit types such as feat, fix, docs, style, refactor, test, and chore. This enforces structured formatting, review, and staging restrictions to ensure proper history readability and collaboration.
The conventional commit format for feature and bug fix scenarios follows the type(scope): description pattern, using feat for features and fix for bug fixes. This standardizes software development workflows requiring structured commit messages with required frontmatter.
To stage files and craft a compliant commit, first review code changes, stage appropriate files, and commit using the conventional format type(scope): description. This disciplined process includes verification steps to ensure proper formatting and safe commits.
Yes, the commit standardization process enforces staging restrictions. It guides through a disciplined process specifying required frontmatter, permissible types, and verification steps to ensure proper formatting, review, and safe commits.
Git workflow commits need required frontmatter and component conventions to ensure traceability and maintainability. Documenting a recommended pattern for adding new components creates consistent, well-structured git commits that improve history readability.
jaqgGroup modified and untracked files into logical git commits and print the command sequence.
gralwebGenerate GitHub pull requests from branch commits using GitHub CLI.
ather-techieGenerate standardized git commit messages from staged changes and repository history.
onbjergGenerates Conventional Commits messages from local change status and diff tools.
