gh:debug-x

Diagnoses and fixes iOS Swift/ObjC bugs using Morph-X blueprints and memory fingerprints.

2|1|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/wangrenzhu-ola/GaleHarnessCodingCLI --skill gh-debug-x
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gh:debug-x
Source: https://github.com/wangrenzhu-ola/GaleHarnessCodingCLI/tree/main/plugins/galeharness-cli/skills/gh-debug-x
Command: npx skills add https://github.com/wangrenzhu-ola/GaleHarnessCodingCLI --skill gh-debug-x

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

gh:debug-x helps engineers diagnose and fix iOS Swift/ObjC bugs using Morph-X blueprints, transforms, audit, and memory fingerprinting to reduce template-code repetition risk.

Core Features & Use Cases

  • End-to-end, phase-driven debugging workflow with guardrails for root-cause analysis and safe fixes
  • Morph-X blueprint-driven transformations and similarity audits to ensure traceable changes
  • Memory-backed retrieval of related context and structured handoff for collaboration

Quick Start

Provide a concise bug description and reproduction steps to begin the Morph-X guided debugging workflow.

Frequently Asked Questions about gh:debug-x

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

FAQPage Schema
How do I diagnose and fix iOS Swift or Objective-C bugs using a structured workflow?▼

To diagnose and fix iOS Swift or Objective-C bugs, use a phase-driven debugging workflow that reproduces issues, traces code paths, applies safe transforms, and audits changes with similarity metrics to reduce template-code repetition risk.

What is a Morph-X blueprint in iOS debugging?▼

A Morph-X blueprint in iOS debugging is a guided framework that drives safe code transformations and similarity audits, ensuring traceable changes and reliable fixes through memory-backed retrieval of related context.

How do I start debugging an iOS project when I have reproduction steps?▼

To start debugging an iOS project, provide a concise bug description and reproduction steps to initiate the guided workflow, which then enforces structured phases and guardrails for root-cause analysis.

Can I use memory fingerprints to trace iOS code paths and prevent repeated template code?▼

Yes, you can use memory fingerprints to retrieve related context and trace iOS code paths, applying similarity audits to catch and reduce template-code repetition risk during transformations.

Does this debugging workflow support both Swift and Objective-C projects?▼

Yes, the debugging workflow supports both Swift and Objective-C iOS projects, applying structured phases, guardrails, and memory-backed context to produce reliable fixes and traceable handoffs across both languages.

What is the best way to ensure safe code transforms and traceable handoffs in iOS bug fixes?▼

The best way to ensure safe code transforms and traceable handoffs is to use a workflow with enforced guardrails and memory-backed context, applying similarity metrics to audit changes and produce reliable fixes.