Forward fix commands to the main /taw router for legacy compatibility.
npx skills add https://github.com/nghiahsgs/taw-kit --skill taw-fix
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
Forward fix commands to the main /taw router to preserve legacy taw-fix behavior.
Invoke taw-fix to forward a fix request to the /taw router.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
nghiahsgsForwards legacy taw-security audit requests to the /taw workflow.
nghiahsgsForward preset-based taw-new requests to the main /taw workflow.
vTRKAGenerate staged deprecation and migration plans with consumer evidence and rollback criteria.
nghiahsgsForward legacy taw-add invocations to the /taw command.
