sl:git

Automate Git workflows with conventional commits, secret scans, and PR creation.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/HuynhHoangPhuc/solon --skill sl-git
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sl:git
Source: https://github.com/HuynhHoangPhuc/solon/tree/main/plugins/solon-core/skills/git
Command: npx skills add https://github.com/HuynhHoangPhuc/solon --skill sl-git

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing Git workflows manually leads to inconsistent commits and potential security risks. This skill enforces conventional commits, automates staging and scanning for secrets, and streamlines PR creation to improve code quality and collaboration.

Core Features & Use Cases

  • Auto-splits commits by scope to keep changes organized and reviewable.
  • Performs pre-commit checks, including secret scans, to prevent risky commits.
  • Supports PR creation via gh integration and enforces standardized messages.
  • Integrates with hooks to automate workflows across teams.

Quick Start

Run sl:git cm to stage, scan, and commit changes, then push or open a PR as needed.

Frequently Asked Questions about sl:git

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

FAQPage Schema
How do I automate conventional commits with secret scanning before pushing?

Automating conventional commits with secret scanning is achieved by running the sl:git cm command to stage changes, perform security checks, and commit. This enforces pre-commit validation to prevent risky commits and streamline workflows.

How do I auto-split commits by scope to keep Git changes organized?

Auto-splitting commits by scope is handled by the automated Git workflow to keep changes organized and reviewable. It enforces scope-aware commit strategies, ensuring standardized messages for feature branches and release planning.

Does automated Git workflow support PR creation via gh integration?

Automated Git workflow supports PR creation via gh integration to streamline code reviews. It enforces standardized messages and automates pull request creation, satisfying requirements for development teams managing feature branches.

What is the best way to enforce pre-commit validation with configured hooks?

The best way to enforce pre-commit validation with configured hooks is to integrate them into the automated Git workflow. This performs secret scans and scope-based checks, preventing risky commits and improving code quality.

Can I use scope-aware commit strategies for development teams managing feature branches?

Scope-aware commit strategies are fully applicable to development teams managing feature branches and release planning. The automated workflow enforces conventional commits and optional push/PR, improving collaboration and code quality.