git-workflow

Stage changes, detect secrets, and auto-split commits in Git workflows.

24|3|Updated Nov 25, 2025
One-click install
npx skills add https://github.com/nguyenthienthanh/aura-frog --skill git-workflow-nguyenthienthanh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/nguyenthienthanh/aura-frog/tree/main/aura-frog/skills/git-workflow
Command: npx skills add https://github.com/nguyenthienthanh/aura-frog --skill git-workflow-nguyenthienthanh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlined, secure Git workflows that minimize token usage and automate commit hygiene while enforcing security checks.

Core Features & Use Cases

  • Commit planning and analysis with grouped changes.
  • Automatic message formatting and sandboxed pushes.
  • Security scanning for secrets before committing.
  • PR workflow guidelines and pre-PR checks.

Quick Start

Stage changes, auto-scan for secrets, and commit with a concise message following the prescribed format.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I prevent secrets from being committed to git?

This Skill scans staged changes for sensitive data before committing, blocking commits that contain secrets. It detects credentials, API keys, and other sensitive information in your working tree and prevents them from reaching the repository.

How can I auto-split commits by file type and scope?

The Skill automatically organizes staged changes into separate commits grouped by file type and scope, enforcing logical separation. This produces cleaner, more reviewable commit history without manual intervention.

What's the best way to enforce consistent commit message formats?

The Skill validates commit messages against predefined types and length constraints, ensuring every commit follows a standardized format. Messages must match allowed types and stay within specified length limits before the commit is allowed.

Can I use automated security checks in CI pipelines and local development?

Yes. The Skill applies security scanning and commit hygiene rules across local development, CI pipelines, and pull request workflows, enforcing the same standards in each environment with minimal token overhead.

How does this approach minimize token usage during git workflows?

The Skill enforces a 2-4 tool-call limit while performing staged analysis, secret detection, commit splitting, and message validation. This constraint ensures efficient processing without excessive API calls or token consumption.

What should I check before pushing changes to a pull request?

The Skill provides pre-PR checks that validate commit messages, verify no secrets are staged, and confirm commits follow scope and type rules. Run these checks before pushing to catch issues early and streamline code review.