playbooks

home / skills / duc01226 / easyplatform / fix

fix skill

/.claude/skills/fix

This skill analyzes issues and routes to specialized fix commands to accelerate debugging and issue resolution.

npx playbooks add skill duc01226/easyplatform --skill fix

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
1.7 KB
---
name: fix
description: "[Fix & Debug] ⚡⚡ Analyze and fix issues [INTELLIGENT ROUTING]"
argument-hint: [issues]
infer: true
---

**Analyze issues and route to specialized fix command:**
<issues>$ARGUMENTS</issues>

## Decision Tree

**1. Check for existing plan:**
- If markdown plan exists → `/code <path-to-plan>`

**2. Route by issue type:**

**A) Type Errors** (keywords: type, typescript, tsc, type error)
→ `/fix-types`

**B) UI/UX Issues** (keywords: ui, ux, design, layout, style, visual, button, component, css, responsive)
→ `/fix-ui <detailed-description>`

**C) CI/CD Issues** (keywords: github actions, pipeline, ci/cd, workflow, deployment, build failed)
→ `/fix-ci <github-actions-url-or-description>`

**D) Test Failures** (keywords: test, spec, jest, vitest, failing test, test suite)
→ `/fix-test <detailed-description>`

**E) Log Analysis** (keywords: logs, error logs, log file, stack trace)
→ `/fix-logs <detailed-description>`

**F) Multiple Independent Issues** (2+ unrelated issues in different areas)
→ `/fix-parallel <detailed-description>`

**G) Complex Issues** (keywords: complex, architecture, refactor, major, system-wide, multiple components)
→ `/fix-hard <detailed-description>`

**H) Simple/Quick Fixes** (default: small bug, single file, straightforward)
→ `/fix-fast <detailed-description>`

## Notes
- `detailed-description` = enhanced prompt describing issue in detail
- If unclear, ask user for clarification before routing
- Can combine routes: e.g., multiple type errors + UI issue → `/fix-parallel`

## IMPORTANT Task Planning Notes

- Always plan and break many small todo tasks
- Always add a final review todo task to review the works done at the end to find any fix or enhancement needed

Overview

This skill analyzes bug reports, logs, and failure descriptions, then intelligently routes the issue to the appropriate specialized fix command. It produces a short plan or asks clarifying questions when input is ambiguous, and always breaks work into small todo tasks with a final review step.

How this skill works

The skill inspects the incoming issue text for keywords and context to determine the type (type error, UI, CI/CD, tests, logs, etc.). If a markdown plan is already present it routes directly to the plan. Otherwise it selects a targeted fix command and prepares a detailed prompt for that command or asks for clarification when needed.

When to use it

  • You have an error message, stack trace, or failing test and need a targeted repair path.
  • Multiple unrelated issues appear and you want parallel handling or combined routing.
  • You want automatic mapping from a problem description to a specialist fixer (types, UI, CI, tests, logs).
  • You have a complex or system-wide issue that needs a staged refactor plan.
  • You want small, testable todos and a final review checklist for applied fixes.

Best practices

  • Provide the full error text, relevant file paths, and any recent changes to improve routing accuracy.
  • If available, include links to CI logs, GitHub Actions workflow files, or failing test output.
  • Describe UI issues with screenshots or a concise visual/behavior description for precise fixes.
  • When multiple distinct issues exist, state them separately so the skill can create parallel routes.
  • Expect a short clarifying question if the description lacks actionable detail.

Example use cases

  • TypeScript compiler errors with several type failures in different files → routes to /fix-types.
  • A failing GitHub Actions deployment with a build error and logs → routes to /fix-ci and /fix-logs as needed.
  • A single-button alignment problem on mobile and CSS responsiveness issues → routes to /fix-ui with details.
  • A suite of unrelated issues (type errors + UI glitch + failing tests) → routes to /fix-parallel with subtasks.
  • A major architecture problem requiring staged refactor and cross-component changes → routes to /fix-hard with a plan.

FAQ

What if the issue description is ambiguous?

I will ask a concise clarifying question before routing to ensure the correct specialist command is chosen.

Can I route multiple issue types at once?

Yes. For multiple independent issues the skill uses /fix-parallel; it can also combine routes when appropriate.