taw-fix

Forward fix commands to the main /taw router for legacy compatibility.

32|13|Updated Apr 21, 2026

Search Tags:#compatibility #migration #CLI #command-routing #shim #taw

Ready to run

npx skills add https://github.com/nghiahsgs/taw-kit --skill taw-fix

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: taw-fix
Source: https://github.com/nghiahsgs/taw-kit/tree/main/skills/taw-fix
Command: npx skills add https://github.com/nghiahsgs/taw-kit --skill taw-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Forward fix commands to the main /taw router to preserve legacy taw-fix behavior.

Core Features & Use Cases

Provides seamless redirection from taw-fix to /taw, preserving user intent and avoiding broken workflows.
Documents deprecation and encourages migration to the /taw fix pathway within the toolkit.

Quick Start

Invoke taw-fix to forward a fix request to the /taw router.

Frequently Asked Questions about taw-fix

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

FAQPage Schema

How do I maintain legacy command compatibility when migrating CLI tools to a new router?▼

To maintain legacy command compatibility, you can use a command-routing shim that forwards legacy invocations like taw-fix to the new /taw router. This preserves backward compatibility and prevents broken workflows during migration.

What is a CLI shim and how does it handle command routing?▼

A CLI shim is a lightweight forwarding mechanism that intercepts commands and redirects them to a primary router. It ensures older commands map to updated pathways without breaking existing user workflows or patch processes.

How do I redirect a deprecated CLI command to a new execution path?▼

Redirect a deprecated CLI command by implementing a shim that forwards the legacy command to the new router path. This approach maintains the original execution intent while guiding users toward the updated toolkit workflow.

Can I use a command shim for error handling and patch workflows without updating scripts?▼

Yes, a command shim allows you to preserve existing error handling and patch workflows without updating scripts. It forwards the original command request directly to the main router, maintaining the expected execution flow.

Are there limitations to using a shim for backward compatibility in CLI migrations?▼

The primary limitation is that a compatibility shim is a temporary bridge. While it successfully forwards commands to the new router, it represents a deprecated pathway and users should eventually migrate directly to the new /taw fix command.