task-effective-git

Restructure Git commits into logical units and manage branches safely.

1|Updated Dec 15, 2025
One-click install
npx skills add https://github.com/Anveio/conveaux --skill task-effective-git
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-effective-git
Source: https://github.com/Anveio/conveaux/tree/main/.claude/skills/task-effective-git
Command: npx skills add https://github.com/Anveio/conveaux --skill task-effective-git

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git.

What problem does it solve?

This Skill automates Git best practices for atomic commits, intentional staging, and safe parallel work patterns.

Core Features & Use Cases

  • Atomic Commits: Automatically restructure commits into logical, reviewable units.
  • Safe Parallel Work: Protect others' work by avoiding destructive Git commands.
  • Use Case: Use before any Git operations to ensure you never accidentally lose work.

Quick Start

Before running git status, add, commit, or push, invoke this Skill to apply safe Git patterns.

Quick Start

When making code changes or creating PRs, use this Skill to maintain clean, understandable Git history.

Frequently Asked Questions about task-effective-git

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

FAQPage Schema
How do I keep Git commits atomic and reviewable when making code changes?

Atomic commits bundle logically related changes into single, self-contained units. This Skill automatically restructures your commits into reviewable chunks, ensuring each commit represents one coherent change. Invoke it before committing to enforce this pattern and maintain clean Git history.

Can I safely work on parallel branches without accidentally losing my team's work?

Yes. This Skill protects shared repositories by preventing destructive Git commands like force push and hard reset. It enforces safe parallel work patterns, so you avoid overwriting others' commits while managing your own branches independently.

What's the best way to stage and commit changes without making mistakes?

Intentional staging—explicitly choosing what goes into each commit—prevents accidental inclusions. This Skill enforces staged commits and validates your changes before pushing, catching errors early and ensuring only intended code reaches the repository.

When should I use this Skill during my Git workflow?

Invoke it before any Git operations: before running status, add, commit, or push. Use it when making code changes, creating pull requests, or whenever you need Git branch operations. Early application prevents mistakes from accumulating.

Does this Skill work with existing Git repositories and workflows?

Yes. This Skill applies to shared repositories and fits into existing workflows without requiring setup changes. It works with standard Git commands and integrates at session start or whenever you request commits, pull requests, or branch operations.

What Git commands does this Skill protect against?

This Skill safeguards against destructive commands like force push, hard reset, and branch deletion that can lose work. It enforces non-destructive history rewrites and two-phase development practices, ensuring repository safety across parallel work.