Run any Skill in Manus with one click

phase-review

Stars6

Forks0

UpdatedMarch 22, 2026 at 19:23

Phase guidance for the neuroflow /review command. Loaded automatically when /review is invoked. Orients Claude for acting as a formal peer reviewer of a colleague's neuroscience paper.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

stanislavjiricek

stanislavjiricek/neuroflow

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Biological Scientists, All OtherLife, Physical, and Social Science Occupations·SOC 19-1029

SKILL.md

readonly

name	phase-review
description	Phase guidance for the neuroflow /review command. Loaded automatically when /review is invoked. Orients Claude for acting as a formal peer reviewer of a colleague's neuroscience paper.

phase-review

Orientation for the /review command. The user is acting as a referee — they are reviewing a colleague's paper, not their own. This is a fundamentally different posture from self-review before submission.

Core orientation

The user is NOT the author. Adopt the perspective of an external referee.
The paper being reviewed belongs to someone else — treat it with rigour, but also fairness.
Calibrate standards to the target journal. A NeuroImage review is not the same as a Scientific Reports review.
The goal is a report the author can act on — specific, prioritised, constructive but unsparing.
Distinguish major issues (must address before acceptance) from minor issues (should address).
Always include a clear recommendation: Accept / Major revision / Minor revision / Reject.

Delegation rule

Do not perform the review directly. Delegate entirely to neuroflow:review-neuro, which contains the full six-area methodology:

Language, style and terminology
Internal consistency and cross-reference integrity
Claim support, causality language and connectivity interpretation
Statistics, network inference and multiple comparisons
Methods reproducibility, reporting standards and open science
Contribution, novelty and journal fit (adversarial referee)

Output

The referee report is saved to .neuroflow/review/review-[paper-title-slug]-[date].md (inside .neuroflow/, as it is a personal work product, not a shareable deliverable)
A ## milestone header is appended to .neuroflow/sessions/YYYY-MM-DD.md including the save path and the recommendation (ACCEPT/REJECT/MAJOR/MINOR) — never paste the full review into the session log

Relevant skills

neuroflow:review-neuro — the core review engine; all six areas live here
neuroflow:neuroflow-core — shared lifecycle rules (read project_config.md and flow.md first; write sessions last)

Slash command

This skill is loaded automatically by /neuroflow:review. If invoked directly without that command, run the full review workflow and mention at the end:

💡 You can also run /neuroflow:review to start the peer review workflow as a slash command next time.

More from this repository

same repository

autoresearch

stanislavjiricek/neuroflow

Infinite improvement loop for any research artifact in any phase — a single managing agent makes one focused change per iteration, judges it against the previous best, keeps or reverts. Its memory is a per-loop wiki it reads before every move and writes after every move. The loop never stops until the human interrupts it. Inspired by Andrej Karpathy's autoresearch (MIT).

2026-06-046

phase-git

stanislavjiricek/neuroflow

Phase guidance for /git — context-aware git shorthand rules, smart push/pull logic, commit message generation, branch management, and PR creation workflow.

2026-06-036

bids

stanislavjiricek/neuroflow

This skill should be used whenever the user mentions BIDS, Brain Imaging Data Structure, BIDS conversion, BIDS validation, BIDS compliance, organizing neuroimaging data, dataset_description.json, participants.tsv, bids-validator, pybids, MNE-BIDS, or asks how to structure EEG/MEG/fMRI/iEEG/PET/DWI data for sharing or preprocessing. Also invoke when the user asks how to name scan files, what sidecar JSON fields are needed, how to set up derivatives/, or how to run fMRIPrep/MRIQC on their dataset. Invoke proactively during /data, /data-preprocess, and /data-analyze phases whenever the dataset structure is relevant to the task at hand.

2026-05-296

phase-data-analyze

stanislavjiricek/neuroflow

Phase guidance for the neuroflow /data-analyze command. Loaded automatically when /data-analyze is invoked to orient agent behavior, relevant skills, and workflow hints for the data-analyze phase.

2026-05-296

phase-data-preprocess

stanislavjiricek/neuroflow

Phase guidance for the neuroflow /data-preprocess command. Loaded automatically when /data-preprocess is invoked to orient agent behavior, relevant skills, and workflow hints for the data-preprocess phase.

2026-05-296

phase-data

stanislavjiricek/neuroflow

Phase guidance for the neuroflow /data command. Loaded automatically when /data is invoked to orient agent behavior, relevant skills, and workflow hints for the data intake phase.

2026-05-296

name	phase-review
description	Phase guidance for the neuroflow /review command. Loaded automatically when /review is invoked. Orients Claude for acting as a formal peer reviewer of a colleague's neuroscience paper.

phase-review

Core orientation

The user is NOT the author. Adopt the perspective of an external referee.
The paper being reviewed belongs to someone else — treat it with rigour, but also fairness.
Calibrate standards to the target journal. A NeuroImage review is not the same as a Scientific Reports review.
The goal is a report the author can act on — specific, prioritised, constructive but unsparing.
Distinguish major issues (must address before acceptance) from minor issues (should address).
Always include a clear recommendation: Accept / Major revision / Minor revision / Reject.

Delegation rule

Do not perform the review directly. Delegate entirely to neuroflow:review-neuro, which contains the full six-area methodology:

Language, style and terminology
Internal consistency and cross-reference integrity
Claim support, causality language and connectivity interpretation
Statistics, network inference and multiple comparisons
Methods reproducibility, reporting standards and open science
Contribution, novelty and journal fit (adversarial referee)

Output

The referee report is saved to .neuroflow/review/review-[paper-title-slug]-[date].md (inside .neuroflow/, as it is a personal work product, not a shareable deliverable)
A ## milestone header is appended to .neuroflow/sessions/YYYY-MM-DD.md including the save path and the recommendation (ACCEPT/REJECT/MAJOR/MINOR) — never paste the full review into the session log

Relevant skills

neuroflow:review-neuro — the core review engine; all six areas live here
neuroflow:neuroflow-core — shared lifecycle rules (read project_config.md and flow.md first; write sessions last)

Slash command

This skill is loaded automatically by /neuroflow:review. If invoked directly without that command, run the full review workflow and mention at the end:

💡 You can also run /neuroflow:review to start the peer review workflow as a slash command next time.