tech-diagnosis-exercise

Generate interactive diagnostic exercises from git commit pairs and problem descriptions.

Updated Jul 5, 2025
One-click install
npx skills add https://github.com/nsuberi/proto-portal-showcase-hub --skill tech-diagnosis-exercise
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-diagnosis-exercise
Source: https://github.com/nsuberi/proto-portal-showcase-hub/tree/main/apps/code-dojo-deprecated/.claude/skills/tech-diagnosis-exercise
Command: npx skills add https://github.com/nsuberi/proto-portal-showcase-hub --skill tech-diagnosis-exercise

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill converts real debugging sessions and git commit pairs into structured, teachable diagnosis exercises so engineers and instructors can turn fixes into learning material that emphasizes systems thinking and troubleshooting patterns.

Core Features & Use Cases

  • Symptom to Exercise: Transform a before/after commit pair and a user problem description into a reproducible symptom narrative and starting question.
  • Layered Technical Anatomy: Produce a layer-by-layer map showing what changed, what didn't, and why—highlighting the negative space for learning.
  • Anatomical Fix & Practice: Include actual code snippets from the after commit, line-by-line explanations, diagnostic questions, and a practice exercise for skill transfer.
  • Use Case: An engineering mentor creates a lesson from a bug fix (local success vs. deployed failure) to teach proxy handling, config issues, or dependency regressions.

Quick Start

Create a diagnosis exercise comparing commits abc123 and def456 describing the observed symptom, environment context, and desired learner level.

Frequently Asked Questions about tech-diagnosis-exercise

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

FAQPage Schema
How do I create debugging exercises from git commit pairs?

To create debugging exercises from git commit pairs, provide a before and after commit hash along with a problem description. The tool generates a structured diagnostic exercise featuring symptom narratives, layer analysis, and practice questions.

What is a git diff diagnostic exercise and when do I need it?

A git diff diagnostic exercise is structured learning material built from before and after code fixes. You need it when transforming real debugging sessions into instructional content that teaches systems thinking and troubleshooting patterns.

How do I turn a bug fix into a teachable troubleshooting scenario?

Turn a bug fix into a teachable scenario by supplying the before and after commits and the observed symptom. The tool maps what changed layer-by-layer, extracts code snippets, and generates learner-focused diagnostic questions.

Can I generate learning materials from git diffs for environment and configuration fixes?

Yes, you can generate learning materials from git diffs for environment, configuration, or code fixes. The tool requires access to both commit states to extract diffs and produce instructional exercises highlighting root causes.

What do I need to generate diagnostic exercises from git history?

You need access to both the before and after commit states, a problem description, the environment context, and the desired learner level. The tool extracts diffs and code snippets to build the exercise anatomy.

Does generating diagnostic exercises from commits work for dependency regression analysis?

Generating diagnostic exercises from commits works for dependency regression analysis by comparing the problematic and fixed commit states. It produces a layer-by-layer map of changes and a practice exercise for skill transfer.