skills.rest
NinaVerde
NinaVerdeCOMMUNITY
Explore all skills by this author →
GitHub

Git Guardian

Enforce staged commits with Conventional Commit messages and verified pushes.

Updated Aug 11, 2025
Search Tags:#git#version-control#conventional-commits#backup-workflow#commit-push#conflict-check
One-click install
npx skills add https://github.com/NinaVerde/ninaverde_app --skill git-guardian
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Git Guardian
Source: https://github.com/NinaVerde/ninaverde_app/tree/main/.agent/skills/git-guardian
Command: npx skills add https://github.com/NinaVerde/ninaverde_app --skill git-guardian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures that work is not left in an incomplete state by guiding users through a disciplined Git backup workflow, preventing lost work.

Core Features & Use Cases

  • Conventional Commits: Enforces standardized commit messages (feat:, fix:, chore:).
  • Staging & Verification: Performs status checks, stages changes, and validates readiness before pushing.
  • Use Case: When preparing a release or collaborating on a feature branch, ensure a clean, traceable commit history.

Quick Start

Run the following sequence in your terminal:

  • git status
  • git add .
  • git commit -m "feat: start using conventional commits"
  • git push origin <branch>

Frequently Asked Questions about Git Guardian

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

FAQPage Schema
How do I enforce conventional commits in my git workflow?▼

Enforcing conventional commits requires using standardized prefixes like feat:, fix:, or chore: in commit messages. This maintains a clean, traceable commit history for feature development and releases.

What is a disciplined git backup workflow to prevent lost work?▼

A disciplined git backup workflow prevents lost work by enforcing a no loose ends policy. It requires performing status checks, staging changes, committing with standardized messages, pushing, and verifying conflicts.

How do I stage and verify changes before a git push?▼

To stage and verify changes before a git push, run a status check to validate readiness, use git add to stage files, and ensure your commit messages follow conventional commit standards before pushing to the branch.

Can I use this for feature branch collaboration without loose ends?▼

Yes, you can use this for feature branch collaboration without loose ends. It applies to collaboration across branches requiring reliable commit history and verified pushes, ensuring no incomplete work is left behind.

Why does my git push workflow need conflict verification?▼

Your git push workflow needs conflict verification to maintain a no loose ends policy and prevent incomplete states. Verifying conflicts after pushing ensures reliable commit history across collaborative branches.

Related Skills

Explore More Software Engineering Skills→
giosuetedeschi-specgiosuetedeschi-spec

git-pushing

Automate git staging, committing, and pushing to remote repositories.

Community
Basic
levkisslevkiss

github

Manage GitHub repositories via GitHub CLI for commits, branches, pull requests, issues, releases, and Pages deployment.

Community
Advanced
RebornQRebornQ
52

trellis-check

Run spec compliance, lint, type-check, and test suites on new changes.

Community
Advanced
sigridjinethsigridjineth
20

git-master

Manage Git repository history with atomic commits and interactive rebasing.

Community
Intermediate