git

Automates git commit, push, PR creation, merge with integrated safety checks.

3|Updated Apr 20, 2026

Search Tags:#git #workflow #safety #commits #merge #pull-request

Ready to run

npx skills add https://github.com/mor-duongmh/morkit-plugin --skill git-mor-duongmh

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git
Source: https://github.com/mor-duongmh/morkit-plugin/tree/main/plugins/morkit/skills/git
Command: npx skills add https://github.com/mor-duongmh/morkit-plugin --skill git-mor-duongmh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps users manage Git operations—commit, push, PR creation, and merges—while enforcing safety checks and standardized conventions to reduce mistakes.

Core Features & Use Cases

Enforces destructive operation confirmations on pushing, force-pushing, and merging into protected branches.
Supports 4 main operations: cm (stage+commit), cp (stage+commit+push), pr (create PR), merge (merge branches).
Applies secret scanning before staging and provides deterministic workflows via the git-manager subagent.
Use Case: A developer on a protected branch wants to push a feature branch after passing secret scans and safety checks with a clear PR description.

Quick Start

Use the git skill to stage changes, create commits, and optionally push or open a PR.

Frequently Asked Questions about git

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

FAQPage Schema

How do I automate git commit and push workflows without accidentally pushing secrets?▼

Automated git workflows can enforce pre-stage secret scanning before staging changes and committing. This prevents sensitive data from entering version control while safely executing your commit and push operations.

How can I safely merge branches and create pull requests on protected branches?▼

Safely merging branches and creating pull requests on protected branches requires enforcing destructive operation confirmations. The workflow intercepts force-pushes and merges to protected branches, prompting validation before proceeding.

How do I enforce conventional commit standards when staging changes?▼

Enforcing conventional commit standards during staging is handled by applying deterministic decision logic to stage changes and generate commits. This standardizes commit messages and reduces formatting mistakes across feature branches.

Can I automate opening pull requests with standard descriptions after committing?▼

Yes, you can automate opening pull requests after committing by chaining stage, commit, and optional push operations. The workflow generates a clear PR description while applying safety checks and environment detection.

What are the limitations of automated git workflows for release branches?▼

Automated git workflows for release branches apply safety constraints by requiring destructive operation confirmations. Users must validate force-pushes and merges, meaning full automation is intentionally limited to prevent accidental data loss.

Do I need any dependencies to run automated git workflows with secret scanning?▼

No dependencies are required to run automated git workflows with secret scanning. The environment detection, staging, and commit logic operates independently without external packages or modules.