rc:commit

Stage, format, and push git changes with conventional commits.

Updated Apr 10, 2026

Search Tags:#automation #git #workflow #security #commit #conventional commits

Ready to run

npx skills add https://github.com/Room-C/ai-dev-workflow --skill rc-commit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rc:commit
Source: https://github.com/Room-C/ai-dev-workflow/tree/main/skills/commit
Command: npx skills add https://github.com/Room-C/ai-dev-workflow --skill rc-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the inconsistency and manual overhead of managing git commits and pushes, ensuring all changes follow the Conventional Commits standard while preventing accidental exposure of sensitive files.

Core Features & Use Cases

Conventional Commit Enforcement: Automatically formats commit messages with proper types and scopes.
Security Guardrails: Scans for and prevents the staging of sensitive files like tokens, credentials, or environment variables.
Use Case: When you have finished a feature or fix, use this skill to safely stage, commit, and push your work to the remote repository without worrying about formatting or accidental secret leaks.

Quick Start

Use the rc:commit skill to stage all changes and push them to the current branch with a conventional commit message.

Frequently Asked Questions about rc:commit

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

FAQPage Schema

How do I automate git commits and pushes with conventional commit formatting?▼

Automating git commits and pushes with conventional commit formatting requires a tool that stages changes, generates properly scoped messages, and pushes to remote repositories. This skill executes that workflow while scanning for sensitive configuration files to prevent accidental credential exposure.

What is the conventional commit format and when do I need it for my git workflow?▼

The conventional commit format standardizes git history by enforcing specific commit types and scopes. You need it for software development workflows requiring consistent commit history, automated changelog generation, and clear semantic versioning tracking across collaborative repositories.

Do I need git and bash utilities to automate staging and pushing changes?▼

You need git, grep, and standard bash utilities to automate staging and pushing changes. These dependencies are required to validate file contents, scan for sensitive environment variables, and execute the version control operations needed for secure conventional commits.

How can I prevent accidental exposure of sensitive files and tokens when pushing to a remote repository?▼

Preventing accidental exposure of sensitive files and tokens when pushing to a remote repository requires scanning staged content for credentials and environment variables before committing. This skill acts as a security guardrail by automatically detecting and blocking sensitive configuration files from being staged.

What's the best way to enforce consistent commit history across a software development team?▼

Enforcing consistent commit history across a software development team is best achieved by automating conventional commit formatting during the staging and pushing process. This ensures all changes follow standard commit types and scopes without relying on manual developer input.