Skip to content

ai4curation/ai-gene-review / .claude/skills/export-proposed-terms

export-proposed-terms

Verified

Export top-level ai-gene-review `proposed_new_terms` entries to a deterministic TSV table.

Export Proposed Terms

Use this skill when the user asks for a TSV or tabular extract of ontology term requests recorded in gene review or module YAML files.

Run the helper from the repository root:

uv run python src/ai_gene_review/tools/export_proposed_terms.py -o reports/proposed_new_terms.tsv

Pass files or directories after the options to restrict the export. With no inputs, the helper scans genes/**/*-ai-review.yaml and modules/**/*.yaml. Module rows carry the module id in review_id and leave the gene and taxon columns empty. The top-level proposed_new_terms list is the canonical place for a term request in both gene reviews and modules.

The TSV defaults to reports/proposed_new_terms.tsv. It has one row per top-level proposed_new_terms entry and skips reviews where proposed_new_terms is empty. It includes:

  • source review fields: source_path, organism, gene_directory, review_id, gene_symbol, taxon_id, taxon_label
  • proposal fields: term_index, proposed_name, proposed_definition, justification, proposed_parent_id, proposed_parent_label
  • structured evidence fields serialized as JSON: proposed_mappings, supported_by

The exporter intentionally ignores knowledge_gaps[].proposed_terms; those are nested gap-specific proposals, not the review's top-level ontology request list. If the user explicitly asks for gap proposals too, write a separate ad hoc extract with a column that distinguishes top-level terms from gap terms.

For custom column order, filtering, or aggregation, treat the generated TSV as a staging table and post-process it with Python's csv module or pandas. Preserve TSV safety by keeping embedded tabs and newlines out of scalar cells.

Treat the TSV as a read-only reporting view, not a round-trip editing source. Scalar columns are whitespace-normalized for tabular readability; nested proposed_mappings and supported_by values are compact JSON for inspection. When updating a review, copy exact supporting_text from the source YAML or publication cache, not from a TSV extract.

receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall