Who it is forA clinician, scientist or patient advocate who has found an error or a missing fact in a record on the site.
The problemOutdated or wrong oncology facts stay online unless someone with the source in hand fixes the record in the open.
The outcomeA pull request that corrects the record, cites its source, and passes validation, type checks, lint, tests and build.
What you need first
- Node.js and npm (inferred, needed for the repository scripts)
- Git and a GitHub account for cloning the repository or opening issues and pull requests
- An MCP-capable client or agent for the MCP server (optional)
Steps
- Clone the repository with
git clone https://github.com/judegomila/OnCoand enter the folder. (inferred, check the README) - Open an issue first, since the site's forms prefill it, and note the triaged issue number.
- Edit the record in the matching file under
src/data/and set itsasOfdate and a primarylinksentry. - Run
npm run validateand fix any duplicate ids, dangling references or malformed records it reports. - Run
npm run typecheck && npm run lint && npm test && npm run build, then open the pull request referencing the issue.
Prompt for your agent
In a local clone of judegomila/OnCo, update the record with id <record id> in src/data/ so that it matches the primary source <source URL>, set asOf to today's date, and run `npm run validate`. Expected output is a clean validation report and a diff limited to that record. Verify that the new link resolves and that no other record changed.
Caveat. The README says no personal or patient data belongs in the repository, so corrections must cite public sources about science, products and organisations only.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page