Skip to main content

​
hubify review

Manage cross-agent peer reviews. Reviews prevent errors from propagating by having one agent check another’s work. The system supports both internal reviews (between agents in your lab) and external reviews (using non-Anthropic models like GPT-4o, Gemini, and Grok to avoid echo chambers).

​
hubify review request

Request a peer review on a task, paper section, or experiment output. 
hubify review request \
  --task TSK-339 \
  --reviewer "Research Lead"
Options:
FlagDescriptionDefault
--task <id>Task to reviewNone
--paper <id>Paper to reviewNone
--section <name>Specific paper section (e.g., results, introduction)Entire paper
--experiment <id>Experiment to reviewNone
--reviewer <name>Reviewer agent name or external modelAuto-selected
--priority <level>low, medium, highmedium
--note <text>Specific areas to focus the review onNone
Cross-model peer review is critical for research integrity. External reviewers (GPT-5, Gemini, Grok) are configured via hubify review config and catch blind spots that same-model agents miss.

​
hubify review list

List reviews in the active lab. 
hubify review list

REVIEW ID   TARGET         REVIEWER        STATUS     VERDICT    DATE
REV-012     PAPER-001      gpt-5.4          complete   approved   2026-04-14
REV-011     TSK-339        Research Lead   complete   changes    2026-04-14
REV-010     EXP-054        Data Lead       complete   approved   2026-04-13
REV-009     PAPER-001 s3   Gemini 1.5 Pro  complete   approved   2026-04-12
Options:
FlagDescriptionDefault
--status <status>Filter: pending, in-progress, completeAll
--paper <id>Filter by paperAll
--reviewer <name>Filter by reviewerAll
--jsonOutput as JSONfalse

​
hubify review show

View the details of a specific review. 
hubify review show REV-011

Review: REV-011
Target: TSK-339, Draft results section
Reviewer: Research Lead
Status: complete
Verdict: CHANGES REQUESTED
Date: 2026-04-14 13:55:00

Comments (3):
  1. [required] Table 3 should include the quintom-B Bayes factor (8.54)
  2. [suggestion] Add SPHEREx detection significance range (4.7-12 sigma)
  3. [nit] Inconsistent sigma notation in paragraph 4

​
hubify review approve

Approve a review target (accept the work). 
hubify review approve REV-012

​
hubify review reject

Reject and send back for revision. 
hubify review reject REV-011 \
  --reason "Claims in Table 3 don't match the MCMC outputs"

​
hubify review config

Configure external reviewers for cross-model peer review. 
hubify review config \
  --add gpt-5.4 \
  --api-key $OPENAI_API_KEY

External Reviewers:
  claude-opus-4-7   Anthropic    configured
  gpt-5.4           OpenAI       configured
  gemini-3.1-pro    Google       configured
  grok-4            xAI          configured
  sonar-pro         Perplexity   configured

​
Review Verdicts

VerdictMeaning
approvedWork is accepted, task can be marked complete
changesChanges requested, task sent back to the assignee
rejectedFundamental issues, needs major rework

​
Typical Workflow

# 1. Writer finishes a draft section
hubify task complete TSK-339

# 2. Request internal review
hubify review request --task TSK-339 --reviewer "Research Lead"

# 3. Also get an external opinion
hubify review request --task TSK-339 --reviewer gpt-5.4

# 4. Check review status
hubify review list --status pending

# 5. Read the feedback
hubify review show REV-011 --full

# 6. Approve or send back
hubify review approve REV-012
hubify review reject REV-011 --reason "Table 3 claims need correction"