Feature request: release-versioned shared Drive output for /internal-module-review
Summary
When multiple editors run /internal-module-review across a release cycle, output DOCXs currently land wherever Claude Code is running. For tracking, it would be useful to them systematically/ automatically written to a release-versioned subfolder on the team's shared Google Drive, so reviews are organized and visible to the whole team without any manual file moving.
Proposed change
Add an optional release argument to the skill invocation:
/internal-module-review "HHV8 Infection" R-HSA-9521541 "Marc Gillespie" 2026-06-16 V95
The skill would write output to:
<configured Drive folder>/V95/Reactome_HHV8Infection_R-HSA-9521541_InternalReview.docx
If the release subfolder does not exist, the skill should create it automatically.
If no release argument is supplied, behaviour should remain as today (output to current working directory).
Suggested implementation
The simplest path requires no API credentials or Python changes: editors who have Google Drive for Desktop installed already have their shared Drive mounted as a local folder. The skill just needs to know the base path (e.g. /Users/[name]/Google Drive/Shared drives/Reactome/Internal Reviews/). This could be:
- Hardcoded in
SKILL.md for the team's specific Drive path, or
- Read from a small local config file (e.g.
~/.config/reactome/skill_config.json) so each editor sets it once.
For teams that want full API-based Drive writing (no Drive for Desktop required), the OAuth pattern already established in /update-gdrive-readme could be extended here.
Why this matters
- Multiple editors can run reviews simultaneously across a release cycle — a shared versioned folder makes the full set of reviews visible to everyone without manual coordination.
- Release-based subfolders (V94/, V95/, etc.) keep the archive clean and make it easy to find reviews for a specific release.
- Filename collisions are already avoided by the existing
Reactome_[PathwayName]_[ReactomeID]_InternalReview.docx naming convention. The only edge case (two editors reviewing the same pathway simultaneously) is unlikely given how reviews are assigned.
Related
The /update-gdrive-readme skill already has working Google Drive OAuth credentials and API calls at ~/.config/reactome/ — if an API-based approach is preferred over Drive for Desktop, the pattern is already established in this repo.
Feature request: release-versioned shared Drive output for
/internal-module-reviewSummary
When multiple editors run
/internal-module-reviewacross a release cycle, output DOCXs currently land wherever Claude Code is running. For tracking, it would be useful to them systematically/ automatically written to a release-versioned subfolder on the team's shared Google Drive, so reviews are organized and visible to the whole team without any manual file moving.Proposed change
Add an optional
releaseargument to the skill invocation:The skill would write output to:
If the release subfolder does not exist, the skill should create it automatically.
If no release argument is supplied, behaviour should remain as today (output to current working directory).
Suggested implementation
The simplest path requires no API credentials or Python changes: editors who have Google Drive for Desktop installed already have their shared Drive mounted as a local folder. The skill just needs to know the base path (e.g.
/Users/[name]/Google Drive/Shared drives/Reactome/Internal Reviews/). This could be:SKILL.mdfor the team's specific Drive path, or~/.config/reactome/skill_config.json) so each editor sets it once.For teams that want full API-based Drive writing (no Drive for Desktop required), the OAuth pattern already established in
/update-gdrive-readmecould be extended here.Why this matters
Reactome_[PathwayName]_[ReactomeID]_InternalReview.docxnaming convention. The only edge case (two editors reviewing the same pathway simultaneously) is unlikely given how reviews are assigned.Related
The
/update-gdrive-readmeskill already has working Google Drive OAuth credentials and API calls at~/.config/reactome/— if an API-based approach is preferred over Drive for Desktop, the pattern is already established in this repo.