commit

Automate secure, convention-compliant Git commits with pre-commit security checks.

37|2|Updated Jun 28, 2025
One-click install
npx skills add https://github.com/jellyrock/jellyrock --skill commit-jellyrock
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/jellyrock/jellyrock/tree/main/.opencode/skills/commit
Command: npx skills add https://github.com/jellyrock/jellyrock --skill commit-jellyrock

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of insecure, inconsistent Git commits by automating pre-commit security checks, enforcing project-specific conventional commit formatting, and intelligently grouping related changes, reducing manual effort and preventing accidental exposure of sensitive data.

Core Features & Use Cases

  • Security Pre-Commit Checks: Automatically detects and fixes debug flags, disabled RALE injection settings, and blocks commits of secrets, locale files, and CI-managed changelogs.
  • Conventional Commit Enforcement: Follows JellyRock-specific commit conventions including type/scope formatting, character limits, and present-tense description rules.
  • Intelligent Change Grouping: Analyzes file modifications to split unrelated changes into separate logical commits or group tightly coupled changes into a single commit to maintain clean project history.
  • Use Case: When working on the JellyRock Roku app, use this Skill to commit a bug fix to the Player component and a separate UI formatting update without mixing them into one messy commit, while ensuring no debug flags are accidentally pushed to the repository.

Quick Start

Use the commit skill to stage and commit all your current uncommitted changes following JellyRock's commit conventions after running all required security validations.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate conventional commit formatting and security checks in Git?

Automate secure conventional commit workflows by validating pre-commit security checks, blocking secret exposure, and enforcing project-specific type/scope formatting to standardize Git commit history.

How do I prevent secrets and debug flags from being pushed to my Git repository?

Prevent accidental secret exposure and debug flag commits by running automated pre-commit security validations that detect sensitive data and disabled RALE injection settings before staging changes.

What is the best way to group related code changes into separate logical Git commits?

Group related code changes into logical Git commits by analyzing file modifications to split unrelated updates or combine tightly coupled changes, maintaining a clean project history without manual effort.

Does this automated commit workflow follow present-tense commit message rules and character limits?

The automated commit workflow enforces conventional commit formatting rules including type/scope structures, character limits, and present-tense descriptions to ensure consistent version control messages.

Can I stage and commit multiple unrelated file modifications without mixing them into one messy commit?

Stage and commit multiple unrelated file modifications by intelligently splitting changes into separate logical commits while simultaneously running required security validations to prevent accidental data exposure.