git-sync-tui-patterns

Standardize git-sync-tui implementation patterns for TUI and CLI workflows.

6|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/KiWi233333/git-sync-tui --skill git-sync-tui-patterns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-sync-tui-patterns
Source: https://github.com/KiWi233333/git-sync-tui/tree/main
Command: npx skills add https://github.com/KiWi233333/git-sync-tui --skill git-sync-tui-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps contributors follow consistent coding patterns and operational conventions so git-sync-tui remains reliable, maintainable, and safe when users cherry-pick commits across repositories with interactive conflict resolution and stash protection.

Core Features & Use Cases

  • Dual-mode architecture conventions (TUI + CLI): Documented routing and separation so shared git logic stays deterministic and UI logic stays isolated.
  • Step state machine workflow: Clear step model guidance for adding or modifying TUI steps without breaking navigation, debouncing, or input readiness.
  • Stash guard safety patterns: Guard-file lifecycle and signal-handling approach for reliable recovery after interruptions.

Use it when you are implementing a new UI step, adding a CLI flag, or extending git operations while preserving the tool’s safety guarantees (backup/rollback, stash guard recovery, and deterministic execution flow).

Quick Start

Ask the AI: “Review the existing git-sync-tui codebase and propose the minimal changes needed to add a new TUI step that fetches additional commit metadata, following the patterns in git-sync-tui-patterns.”

Frequently Asked Questions about git-sync-tui-patterns

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

FAQPage Schema
How do I add a new TUI step to a git sync workflow without breaking existing navigation?

A step state machine structure standardizes adding TUI steps by modeling sequential git commit synchronization phases, ensuring deterministic execution flow and input readiness without breaking existing navigation or debouncing.

What is a stash guard lifecycle and when do I need it for git operations?

A stash guard lifecycle manages signal-handling and guard-file recovery for git operations, ensuring reliable state restoration after interruptions. You need it when extending git operations to preserve backup and rollback safety guarantees.

How do I separate interactive TUI logic from non-interactive CLI git commit synchronization?

Separate interactive TUI logic from non-interactive CLI git commit synchronization using a dual-mode architecture. This routing convention isolates UI logic while keeping shared git logic deterministic across both execution paths.

Can I use TypeScript ESM conventions to implement git cherry-pick conflict resolution patterns?

Yes, you can implement git cherry-pick conflict resolution patterns using strict TypeScript and ESM conventions. This approach maintains type safety and module isolation when extending interactive conflict resolution and stash protection workflows.

Why do my git sync workflows fail to recover after a signal interruption during cherry-picking?

Git sync workflows fail to recover after signal interruptions if they lack stash guard safety patterns. Implementing guard-file lifecycle handling ensures reliable backup and rollback behavior, allowing state restoration after unexpected process termination.

What's the best way to standardize coding standards for a dual-mode git CLI and TUI tool?

The best way to standardize coding standards for a dual-mode git CLI and TUI tool is enforcing strict TypeScript ESM conventions alongside a step state machine structure. This maintains deterministic execution, UI isolation, and reliable safety guardrails.