Git Workflow Trigger

Name: Git Workflow Trigger
Author: majiayu000

ASecurity

Natural language wrapper for git commands - automatically triggers /git:commit, /git:status, /git:push when users express git workflow intent

666 stars
0 votes
0 copies
3 views
Added February 8, 2026

toolsexpressrailsgit

Security analysis

A100/100

Scanned February 12, 2026

npx -y skills add majiayu000/claude-skill-registry --skill git-workflow-trigger --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Git Workflow Trigger?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Git Workflow Trigger

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/majiayu000-git-workflow-trigger/badge)](https://www.skillsdirectory.com/skills/majiayu000-git-workflow-trigger)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
name: git-workflow-trigger
description: Natural language wrapper for git commands - automatically triggers /git:commit, /git:status, /git:push when users express git workflow intent
schema_version: 1.0
---

# git-workflow-trigger

**Type:** WRITE-CAPABLE
**DAIC Modes:** IMPLEMENT only
**Priority:** Medium

## Trigger Reference

This skill activates on:
- **Keywords:** "commit changes", "save changes", "create commit", "git status", "show changes", "push changes", "commit this", "save work", "git commit", "push to remote", "push work"
- **Intent Patterns:** `(commit|save).*?(changes|work)`, `create.*?commit`, `(show|display|check).*(changes|status)`, `push.*?(changes|to remote|work)`

From: `skill-rules.json` - git-workflow-trigger configuration

## Purpose

Automatically trigger git commands (`/git:commit`, `/git:status`, `/git:push`) when users express git workflow intent using natural language.

**Important:** This skill is classified as WRITE-CAPABLE and only triggers in IMPLEMENT mode, even for read-only operations like `git status`. This is intentional to keep git operations grouped together. If you need git status outside IMPLEMENT mode, use the `/git:status` command directly.

## Core Behavior

1. **Git Workflow Detection**
   - Detect git operations from natural language
   - Route to appropriate git command based on intent

2. **Command Routing**
   - **Commit:** "commit changes" → `/git:commit`
   - **Status:** "show changes" → `/git:status`
   - **Push:** "push changes" → `/git:push`

3. **Mode Restriction**
   - This skill only triggers in IMPLEMENT mode (WRITE-CAPABLE classification)
   - All git operations (including status) are grouped together
   - For git status outside IMPLEMENT mode, use `/git:status` directly

## Natural Language Examples

**Triggers this skill:**
- ✓ "Commit my changes"
- ✓ "Save work and commit"
- ✓ "Show my changes"
- ✓ "Push to remote"
- ✓ "Git status"

## Safety Guardrails

**WRITE-CAPABLE RULES:**
- ✓ Only write operations in IMPLEMENT mode
- ✓ Verify active task for commits
- ✓ Read operations (status) allowed in any mode