auto-fix

Route alias prompts to the canonical auto router for bug-fix workflows.

106|74|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/Insajin/autopus-adk --skill auto-fix-insajin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto-fix
Source: https://github.com/Insajin/autopus-adk/tree/main/.autopus/plugins/auto/skills/auto-fix
Command: npx skills add https://github.com/Insajin/autopus-adk --skill auto-fix-insajin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Thin alias shim that routes requests to the canonical auto router, ensuring a consistent entry point for bug-fix workflows and branding.

Core Features & Use Cases

  • Thin alias shim: forwards $auto-fix to the auto router with exact flags preserved.
  • Hand-off to detailed workflow: after context load and SPEC path resolution, the router loads the auto-fix workflow.
  • Branding and consistency: ensures responses start and end with the canonical Autopus banner as per policy.

Quick Start

Invoke the canonical router by loading the auto skill and continue with the detailed auto-fix workflow.

Frequently Asked Questions about auto-fix

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

FAQPage Schema
What is a thin alias shim for routing bug-fix workflows?

A thin alias shim redirects prompt requests to a canonical auto router, ensuring a consistent entry point for bug-fix workflows while preserving original flags and context.

How do I standardize bug-fix workflow entry points using an alias?

Invoke the canonical router through the alias shim to load the detailed auto-fix workflow after resolving SPEC paths and restoring context, standardizing the bug-fix entry point.

Does the auto-fix alias shim preserve command flags during workflow handoffs?

Yes, the auto-fix alias shim forwards requests to the auto router with exact flags preserved, ensuring no context or parameters are lost during the workflow handoff.

Can I use this alias shim to enforce consistent branding in automated routing?

Yes, the alias shim ensures responses start and end with the canonical Autopus banner, enforcing branding and consistency policies across the standardized bug-fix workflow.

When do I need context restoration before delegating to an auto-fix workflow?

Context restoration and SPEC path resolution are required before the alias shim can safely delegate requests to the detailed auto-fix workflow for bug resolution.

What's the best way to route prompts to a canonical auto router?

Using a thin alias shim is the best way to route prompts to a canonical auto router, as it standardizes the workflow entry point while maintaining original request flags and context.