commit

Review staged Git changes, scan for secrets, and commit with conventional messages.

1|Updated Dec 1, 2025

Search Tags:#git #workflow #code review #version control #security #commit

Ready to run

npx skills add https://github.com/hypeJunction/ai-assistant-starter --skill commit-hypejunction

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/hypeJunction/ai-assistant-starter/tree/main/skills/commit
Command: npx skills add https://github.com/hypeJunction/ai-assistant-starter --skill commit-hypejunction

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill ensures your code changes are committed safely and effectively, preventing accidental secrets from being exposed and maintaining a clean commit history.

Core Features & Use Cases

Secure Commits: Scans for and blocks commits containing secrets like API keys or passwords.
Change Review: Presents your staged changes for review before committing.
Commit Message Guidance: Helps you write clear, conventional commit messages.
Use Case: You've finished a feature and want to save your work. This Skill will show you what you've changed, scan for any accidental secrets, and help you craft a descriptive commit message before finalizing the commit.

Quick Start

Use the commit skill to review and save your staged changes.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I scan staged git changes for secrets before committing?▼

To scan staged git changes for secrets before committing, this Skill reviews your Git diffs and status, automatically detecting insecure patterns like API keys or passwords, and blocks the commit execution if any secrets are found.

What is the best way to enforce conventional commit messages in git?▼

The best way to enforce conventional commit messages in git is to use a workflow tool that guides you through crafting clear commit messages and validates them against conventions before finalizing your staged code changes to the repository.

How does a secure git commit workflow handle code review?▼

A secure git commit workflow handles code review by presenting staged modifications for user confirmation before execution, ensuring you review exactly what changed in your code before the commit is applied to the repository.

Can I apply tiered validation to my version control commits?▼

You can apply tiered validation to version control commits by configuring optional validation steps based on change tier, allowing the commit process to enforce different security and review rules depending on the modification scope.

Why would a git commit be blocked during version control?▼

A git commit would be blocked during version control when security scans detect secrets or insecure patterns within the staged code changes, preventing accidental exposure of sensitive data until the issues are resolved.

Does the commit workflow require any external dependencies to run?▼

The commit workflow does not require any external dependencies to run, as it operates directly on Git diffs and status using internal scripts and references to manage security scans and commit message conventions.