skills.rest
tktcorporation
tktcorporationCOMMUNITY
Explore all skills by this author →
Website𝕏@tktcorporationGitHub

upstream-fix

Identify and plan upstream root-cause fixes across multi-module data flows.

2|Updated Feb 27, 2026
Search Tags:#refactor#code-quality#root-cause#bug-fix#design-improvement#upstream-fix
One-click install
npx skills add https://github.com/tktcorporation/cross-recorder --skill upstream-fix
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: upstream-fix
Source: https://github.com/tktcorporation/cross-recorder/tree/main/.claude/skills/upstream-fix
Command: npx skills add https://github.com/tktcorporation/cross-recorder --skill upstream-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Upstream-fix provides a disciplined workflow to address bug reports at the design/architecture level, prioritizing root-cause resolution over quick, local patches to reduce recurrence and technical debt.

Core Features & Use Cases

  • Phase 1: 現状把握 - Gather historical context, surrounding code paths, data flow, and prior fixes to understand the symptom and potential upstream origin.
  • Phase 2: 診断 - Distill symptom, direct cause, root cause, and impact to create a clear problem map for decision making.
  • Phase 3: 設計判断 - Propose structural changes and refactors that elevate responsibilities, normalize data, and align contracts across modules.
  • Phase 4: 提案 - Provide actionable options (A: full upstream overhaul, B: upstream-focused fixes, C: targeted local patch) with trade-offs and risk assessment.
  • Phase 5: 実装 - Implement chosen approach with traceability, testing, and documentation of rationale.

Quick Start

Follow the workflow to determine whether an upstream fix is appropriate and outline concrete implementation steps.

Frequently Asked Questions about upstream-fix

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

FAQPage Schema
What is an upstream root cause fix in software maintenance?▼

An upstream root cause fix resolves bugs at the design or architecture level rather than applying surface-level patches. This approach normalizes data flows and aligns module contracts to prevent recurrence and reduce technical debt.

How do I decide between a root cause refactor and a local bug patch?▼

Diagnose the symptom, direct cause, and root cause to map the problem. Evaluate structural changes against local patches using a risk assessment, weighing trade-offs between immediate fixes and long-term design improvements.

How do I implement an upstream fix across multi-module data flows?▼

Gather historical context and trace data paths to understand the symptom. Propose structural changes that elevate responsibilities and normalize data, then implement with traceability, testing, and documented rationale.

When should I avoid upstream design changes for bug triage?▼

Avoid upstream design changes when risk assessment indicates high disruption to multi-module data flows. Opt for a targeted local patch to mitigate immediate impact while documenting the rationale for deferring structural overhauls.

What is the best way to prevent recurring bugs in multi-module architectures?▼

The best way to prevent recurring bugs is applying design governance to elevate responsibilities and align contracts across modules. Prioritize upstream-focused fixes over quick patches to eliminate root causes and reduce technical debt.

Related Skills

Explore More Software Engineering Skills→
aimasteraccaimasteracc
46

investigate

Identifies and analyzes root causes of software bugs through structured investigation.

Community
Advanced
ssimhanssimhan
1

kaizen

Identify small, atomic code improvements with documented rationale and impact.

Community
Basic
AvihusittonAvihusitton

brooks-lint

Review code for design smells, coupling issues, and architectural risks.

Community
Intermediate
MykhailoDmytriakhaMykhailoDmytriakha

30-analyze-impact-150

Map upstream dependencies, downstream impact, and blast radius of system changes.

Community
Advanced