Natural language wrapper for git commands - automatically triggers /git:commit, /git:status, /git:push when users express git workflow intent
Scanned 2/12/2026
Install via CLI
openskills install majiayu000/claude-skill-registry---
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
No comments yet. Be the first to comment!
Playbook for creating and editing uCoz landing pages via MCP tools (`templates_tool`, `ftp_tool`, `modules_tool`). Use for tasks such as: "build a landing page", "update the homepage as a landing page", "create a promo page on the homepage", "add a lead form / menu / SEO to the homepage". Homepage: `page_list`, `page_get`; first publish — `page_update` with full `page_tmpl`; HTML edits after generation — `patch_template` (module_id=2, template_id=1), not `update_template`. Activate the mail f...
Interact with the Paperclip control plane API to manage tasks, coordinate with other agents, and follow company governance. Use when you need to check assignments, update task status, delegate work, post comments, set up or manage routines (recurring scheduled tasks), or call any Paperclip API endpoint. Do NOT use for the actual domain work itself (writing code, research, etc.) — only for Paperclip coordination.
Digital Audio Workstation usage, music composition, interactive music systems, and game audio implementation for immersive soundscapes.
Instantly.ai cold email outreach API - manage campaigns, leads, accounts, and analytics. Use for cold email automation, lead management, campaign creation/monitoring, and email account warmup.
Run a single Terminal-Bench problem through Paperclip in a bounded, human-in-the-loop improvement cycle until the smoke passes, the board rejects the next fix, the iteration budget is exhausted, or a real blocker is named. Each iteration runs a bounded smoke against an isolated Paperclip App worktree, captures artifacts, diagnoses the exact stop point with `/diagnose-why-work-stopped`, requests board confirmation before any product fix, then reruns against the same worktree. Use whenever an i...