commit

Name: commit
Availability: InStock
Author: cloudvoyant

Create conventional Git commits with pre-commit hooks and CI monitoring.

Updated Nov 15, 2025

Search Tags:#automation #git #code review #commit #conventional commits #ci

Ready to run

npx skills add https://github.com/cloudvoyant/claudevoyant --skill commit-cloudvoyant

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/cloudvoyant/claudevoyant/tree/main/plugins/dev/skills/commit
Command: npx skills add https://github.com/cloudvoyant/claudevoyant --skill commit-cloudvoyant

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of professional, conventional Git commit messages, ensuring consistency and adherence to best practices, while also monitoring CI status post-push.

Core Features & Use Cases

Conventional Commits: Generates commit messages following the conventional commit specification.
Automated Formatting & Linting: Runs formatters and linters before staging to ensure code quality.
Secret Detection: Prevents accidental staging of sensitive files.
CI Monitoring: Pushes commits and monitors GitHub Actions or GitLab CI status in the background.
Use Case: After completing a feature, use this Skill to generate a feat: commit, automatically stage all changes, push to the remote, and then get notified when the CI checks pass or fail.

Quick Start

Use the commit skill to create a new feature commit for the staged changes.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I automate conventional commits with pre-commit hooks for formatting and linting?▼

Automating conventional commits involves generating specification-compliant messages while running pre-commit hooks for formatting, linting, and secret detection before staging changes. This Skill enforces code quality and streamlines the entire commit process automatically.

What is the best way to monitor GitHub Actions or GitLab CI status automatically after pushing a commit?▼

Monitoring CI status post-push is handled by automatically pushing commits to the remote and monitoring GitHub Actions or GitLab CI pipelines in the background. You receive notifications when the CI checks pass or fail.

How do I prevent accidental staging of sensitive files and secrets in Git?▼

Preventing accidental staging of sensitive files requires pre-commit secret detection. This Skill integrates secret detection into the Git workflow to scan and block sensitive files before the commit is created.

Can I use this conventional commit automation without manually staging files first?▼

Yes, conventional commit automation supports atomic commits by automatically staging all changes. After completing a feature, it generates the commit, stages the files, pushes to the remote, and monitors CI without manual staging.

Does this Git commit automation support autofixing when CI checks fail?▼

Yes, Git commit automation provides optional autofixing for CI failures. After monitoring the pipeline status in the background, it can automatically address and resolve CI check failures when enabled.