git-workflow

Enforce safe Git branch operations across INAV repositories.

4|2|Updated Nov 30, 2025
One-click install
npx skills add https://github.com/sensei-hacker/inav-claude --skill git-workflow-sensei-hacker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/sensei-hacker/inav-claude/tree/main/.claude/skills/git-workflow
Command: npx skills add https://github.com/sensei-hacker/inav-claude --skill git-workflow-sensei-hacker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill simplifies common Git operations across the multi-repository INAV project, reducing the complexity and potential for errors when managing branches and code changes.

Core Features & Use Cases

  • Branch Management: Create new branches, switch between existing ones, and safely handle uncommitted changes.
  • Status Checks: Get comprehensive summaries of your working tree, including staged/unstaged changes and remote tracking.
  • Multi-Repo Operations: Perform git status checks and create matching branches across inav/, inav-configurator/, and inavwiki/ simultaneously.
  • Use Case: A developer needs to create a new feature branch for a bug fix, check the status of their changes across all INAV repositories, and then push their work to the remote.

Quick Start

Create a new git branch called 'feature-new-gps'.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I safely create and switch between branches across multiple Git repositories?

Branch creation and switching across INAV repositories enforces explicit base-branch specification and naming conventions to prevent unsafe operations. The Skill guides you through creating matching branches on inav, inav-configurator, and inavwiki simultaneously, then validates the switch before proceeding.

What's the best way to check Git status across multiple INAV repositories at once?

Comprehensive status checks summarize your working tree across all three INAV repositories in one operation, showing staged and unstaged changes, remote tracking, and uncommitted work. This eliminates checking each repository individually and catches divergent states.

How do I prevent destructive Git operations when managing INAV code changes?

Git workflow safeguards enforce non-destructive practices by validating operations before execution, preserving commit history, and guiding safe push and merge procedures. It blocks unsafe commands and suggests correct alternatives aligned with INAV project conventions.

Can I manage branches consistently across the inav, inav-configurator, and inavwiki repositories?

Yes. The Skill performs multi-repository operations that create and manage matching branches across all three INAV repositories with unified naming conventions, ensuring consistency and reducing manual synchronization errors.

What Git workflow practices does this Skill enforce for INAV development?

The Skill enforces branch naming conventions, explicit base-branch specification, non-destructive workflows, commit history preservation, and safe review practices. It prevents common errors and guides developers toward established INAV project standards.