skills.rest
I7T5
I7T5COMMUNITY
Explore all skills by this author →
WebsiteGitHub

edmund-live-repro-and-diagnostics

Diagnose and reproduce live bugs in the Edmund Markdown editor using diagnostic traces and scripts.

164|13|Updated Apr 1, 2026
Search Tags:#code analysis#bug tracking#bug reproduction#markdown editor#diagnostic tools
One-click install
npx skills add https://github.com/I7T5/Edmund --skill edmund-live-repro-and-diagnostics
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: edmund-live-repro-and-diagnostics
Source: https://github.com/I7T5/Edmund/tree/main/.agents/skills/edmund-live-repro-and-diagnostics
Command: npx skills add https://github.com/I7T5/Edmund --skill edmund-live-repro-and-diagnostics

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires scripts/check-live-instance.sh, scripts/grep-trace.sh, scripts/capture-window.sh, scripts/launch-debug.sh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps diagnose and reproduce bugs in the Edmund Markdown editor, ensuring accurate identification and resolution of issues.

Core Features & Use Cases

  • Bug Reproduction: Offers a structured approach to reproduce bugs that involve live behavior in the editor.
  • Diagnostic Tools: Provides tools for interpreting diagnostic traces and driving the running app with scripts.
  • Use Case: When encountering a bug that cannot be replicated in a unit test, this skill can help identify the root cause and provide a reproducible scenario.

Quick Start

To measure Edmund and reproduce a bug, load the skill and follow the diagnostic steps outlined in the SKILL.md file.

Frequently Asked Questions about edmund-live-repro-and-diagnostics

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

FAQPage Schema
How do I reproduce bugs in the Edmund Markdown editor that cannot be replicated in a unit test?▼

Reproduce Edmund Markdown editor bugs by loading the skill and following diagnostic steps to drive the running app with scripts. This captures live behavior traces to identify root causes and build a reproducible scenario for issues evading unit tests.

What is the best way to diagnose live behavior issues in a Markdown editor?▼

Diagnose live behavior issues by using dedicated diagnostic tools to capture window states and interpret trace logs from the running app. This pinpoints exact runtime conditions causing bugs, ensuring accurate identification and resolution of the editor issue.

Do I need the Edmund editor running to capture diagnostic traces?▼

Yes, you need the Edmund Markdown editor running and configured for diagnostic logging to capture live traces. The diagnostic scripts interact directly with the active application to measure behavior and reproduce the specific bug scenario accurately.

How do I use diagnostic scripts to track and reproduce code bugs?▼

Use diagnostic scripts to launch the debugger, capture active window states, and grep through trace logs to track code bugs. This structured workflow interprets live diagnostic data to isolate the root cause of the runtime behavior issue.

What are the limitations of bug reproduction using diagnostic logging?▼

Bug reproduction using diagnostic logging requires the application to be actively running and properly configured for trace output. It may not capture issues occurring in unmonitored background processes or environments lacking diagnostic logging support.

Related Skills

Explore More Software Engineering Skills→
I7T5I7T5
164

edmund-config-and-flags

Catalog configuration options and flags in the Edmund Markdown editor.

Community
Advanced
kabakakabaka

rca-investigation

Guide structured root cause analysis with a 5-step process and report template.

Community
Advanced
ArabelaTsoArabelaTso
142

bug-reproduction-test-generator

Generate executable regression tests from bug reports and stack traces.

Community
Intermediate
sipherxyzsipherxyz
1

live-coding-refresh

Trigger Unreal Engine Live Coding compilation via Ctrl+Alt+F11 keystroke.

Official
Basic