Skip to content

ai4curation/ai-gene-review / .claude/skills/gocam-curation

gocam-curation

Verified

Evaluate and review GO-CAM (Gene Ontology Causal Activity Model) activities / annotons — molecular-function typing, has-input, causal relations, complexes, evidence — and check their consistency with gene annotation reviews. Use when reviewing cached GO-CAMs under gocams/, filling a GoCamReview YAML (gocams/<id>/<id>-review.yaml), or grounding a module in GO-CAM models.

references/complexes.md

View on GitHub
# Complexes

How a protein complex's activity is attributed determines whether the model is
informative. A mismatch is QC flag `COMPLEX_SUBUNIT_REPRESENTATION`.

## Three cases

1. **Known active subunit** — when one subunit carries the catalytic/transport/
   binding activity, represent **that specific gene product** as `enabled_by`,
   not the complex. (e.g. attribute the kinase activity to the catalytic
   subunit, not the holoenzyme.)
2. **Unknown active subunit** — when the activity cannot be attributed to a
   specific subunit, use the **GO complex term** as the enabler.
3. **Shared / multi-subunit activity** — when several subunits genuinely
   contribute to the activity, represent the relevant contributing subunits.

## How this maps to our model representation

In our module schema, a complex is a `ProteinComplexDescriptor`; role-bearing
components surface via `active_units`. When grounding a module annoton in a
GO-CAM activity, prefer the GO-CAM that attributes the activity to the correct
subunit (case 1) over one that uses the bare complex term, unless the subunit is
genuinely unknown.

## Check

- Is the activity attributed to the subunit that actually performs it?
- If the complex term is used, is that because attribution is truly unclear (OK)
  or because the curator defaulted to it (flag it)?
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