Skip to content

Add HPO AI Assistant GitHub workflow#11437

Draft
justaddcoffee wants to merge 1 commit into
obophenotype:masterfrom
justaddcoffee:feature/hpo-ai-assistant
Draft

Add HPO AI Assistant GitHub workflow#11437
justaddcoffee wants to merge 1 commit into
obophenotype:masterfrom
justaddcoffee:feature/hpo-ai-assistant

Conversation

@justaddcoffee

Copy link
Copy Markdown

Summary

  • Add draft plan for an AI-powered GitHub bot to help with HPO ontology curation
  • Bot would trigger on @mentions and help with:
    • Creating new HPO terms
    • Editing existing terms
    • Answering questions about HPO

Status

Draft - Planning phase. See notes/hpo-ai-assistant-plan.md for implementation options.

Implementation Options

Comparing two existing implementations:

  1. Mondo approach - dragon-ai-agent/run-goose-obo (simpler)
  2. Data-Sheets-Schema approach - dragon-ai-agent/run-claude-obo (more sophisticated)

Next Steps

  • Decide on implementation approach
  • Get list of authorized users
  • Write HPO-specific AI instructions
  • Create workflow file
  • Set up required secrets
  • Test on fork before merging

🤖 Generated with Claude Code

Document implementation options for a GitHub workflow that triggers
on @mentions to help with creating/editing HPO terms and answering
questions. Compares Mondo and Data-Sheets-Schema approaches.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@pnrobinson

Copy link
Copy Markdown
Contributor

@justaddcoffee @hansenp Please can we do this with issues and not pull requests? PRs are essentially useless with OWL files, and nearly always we may want to polish or revise even relatively good suggestions!

@justaddcoffee

Copy link
Copy Markdown
Author

Sure, I think it's easy enough to constrain the agent to only make issues. Maybe we could walk through a few examples of what sort of OWL changes we want to come out the other end

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants