skills.rest
Veloxia-agency
Veloxia-agencyCOMMUNITY
Explore all skills by this author →
GitHub

focused-fix

Trace scope, diagnose root causes, and verify fixes across a codebase.

Updated Apr 24, 2026
Search Tags:#debugging#root cause#verification#codebase analysis#dependency tracing#feature repair
One-click install
npx skills add https://github.com/Veloxia-agency/VELOXIA-WEB --skill focused-fix-veloxia-agency
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: focused-fix
Source: https://github.com/Veloxia-agency/VELOXIA-WEB/tree/main/.claude/skills/engineering/skills/focused-fix
Command: npx skills add https://github.com/Veloxia-agency/VELOXIA-WEB --skill focused-fix-veloxia-agency

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps repair a broken feature, module, or workflow by tracing the full scope of the issue before any code changes are made. It is designed for situations where a partial fix is not enough and the entire area must work reliably from start to finish.

Core Features & Use Cases

  • Systematic feature repair: Maps the full boundary of the affected area, including entry points, internal files, and every dependency.
  • Root-cause diagnosis: Checks imports, types, runtime configuration, logs, tests, and recent changes to confirm what is actually broken.
  • Safe, ordered fixes: Applies dependency, type, logic, test, and integration repairs in sequence to minimize regressions.
  • Example use case: Use it when a login flow, checkout path, or dashboard module is failing across multiple files and needs an end-to-end recovery plan.

Quick Start

Ask the assistant to focus on the broken feature or folder and follow a full scope, trace, diagnose, fix, and verify repair process.

Frequently Asked Questions about focused-fix

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

FAQPage Schema
How do I debug a broken feature across multiple files in my codebase?▼

End-to-end feature repair traces the full boundary of a broken module, including entry points, internal files, and dependencies, to restore correct behavior reliably for all consumers without introducing regressions.

What's the best way to find the root cause of a failing workflow integration?▼

The best way to find the root cause of a failing workflow integration is to systematically check imports, runtime configuration, logs, tests, and recent changes to confirm what is actually broken before applying fixes.

How do I fix a broken login or checkout flow without introducing regressions?▼

You can use this systematic diagnosis approach to repair shared components and broken modules by tracing scope, dependencies, root causes, and verification across the entire codebase.

Why does my partial fix not resolve the broken module behavior completely?▼

A partial fix fails to resolve broken module behavior when the entire area must work reliably from start to finish, requiring a full scope trace and end-to-end recovery plan rather than isolated changes.

Related Skills

Explore More Software Engineering Skills→
kslhunterkslhunter
2

sd-explore

Trace code execution paths from entry points to data storage.

Community
Advanced
axiomanticaxiomantic
8

test-driven-development

Enforce a red-green-refactor workflow by writing failing tests before production code.

Official
Intermediate
Marshall-HallenbeckMarshall-Hallenbeck
5

review

Analyze uncommitted git diffs for bugs, vulnerabilities, and maintainability issues.

Community
Advanced
zhentingWu-wztzhentingWu-wzt
6

comet-hotfix

Automate minor bug fix lifecycle with Comet state management and verification.

Community
Advanced