GitHub Issue Analysis FAQs

Question 1

Does this skill require specific environment access?

Accepted Answer

Yes, it utilizes the GitHub CLI (gh) for issue management and requires access to domain-specific tools like obo-grepl.obo and the local ontology source patterns to function at peak accuracy.

Question 2

What does the GitHub Issue Analysis skill do?

Accepted Answer

This skill enables Claude to analyze GitHub issues related to disease ontologies (like MONDO). It validates medical and terminological requests, identifies optimal design patterns, and generates structured Markdown reports featuring Mermaid relationship diagrams.

Question 3

When should I use this skill in my workflow?

Accepted Answer

Use this skill when triaging GitHub issues that propose new disease terms, parent-child relationship changes, or classification updates. It is particularly effective for bio-curators and ontology engineers working within the Monarch Initiative or OBO Foundry ecosystems.

Question 4

How does this skill improve the curation process?

Accepted Answer

It automates the tedious parts of curation: it searches for optimal parent terms using tools like obo-grepl.obo, checks for existing design patterns (DOSDP), and handles GitHub CLI operations like viewing issues and posting comments with structured evidence.

Question 5

What specific technical features are included?

Accepted Answer

Key features include automated Mermaid diagram generation for visualizing proposed hierarchy changes, duplication checks, identifier validation, and the ability to propose logical and human-readable definitions based on clinical justifications.

GitHub Issue Analysis

GitHub Issue Analysis

主要功能

使用场景

主要功能

使用场景