git

Automate Git workflows with conventional commits, staging, pushing, PRs, and merges.

2|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/NammDev/Goads-Krea --skill git-nammdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git
Source: https://github.com/NammDev/Goads-Krea/tree/main/.claude/skills/git
Command: npx skills add https://github.com/NammDev/Goads-Krea --skill git-nammdev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Git operations can be error-prone and time-consuming when enforcing conventional commits, staging, committing, pushing, PRs, and merges, and when scanning for secrets before commits.

Core Features & Use Cases

  • Auto-splits commits by type and scope to keep history clean.
  • Isolates git workflows via a git-manager subagent for safer, quieter operations.
  • Security scans for secrets before commit to prevent leakage.

Quick Start

Initiate a standard git workflow using the git-manager subagent to stage, commit with conventional formatting, and push.

Frequently Asked Questions about git

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

FAQPage Schema
How do I automate safe git workflows with conventional commits?

Automate safe git workflows by staging, committing, pushing, and managing PRs using a subagent that enforces conventional commit format checks and scans for secrets before committing.

What is the best way to prevent secret leakage before pushing commits?

To prevent secret leakage before pushing commits, use a workflow that performs automatic security scans for secrets prior to the commit operation.

How does auto-splitting commits by type and scope keep git history clean?

Auto-splitting commits by type and scope keeps git history clean by categorizing changes into isolated commits, enforcing consistency across branches and pull requests.

Can I isolate git operations to run quietly in the background?

You can isolate git operations by using a git-manager subagent to coordinate staging, committing, and pushing, ensuring safer and quieter workflow execution.

Does this git workflow tool enforce consistency across pull requests?

Yes, the workflow enforces consistency across pull requests by applying conventional format checks and coordinating merges through an isolated subagent.

What are the limitations of using a subagent for git merge and push operations?

Using a subagent for git merge and push operations isolates the process for safety, but relies on the subagent to correctly coordinate steps and enforce conventional formats without manual intervention.