Academic Lab Open-Source Release Review Framework
Develop an end-to-end peer review plan for transitioning graduate student research code into an open-source library.
Use this template when preparing university lab software for public open-source publication. It structures documentation, licensing, test coverage, and code hygiene reviews across distributed student contributors.
Role: Senior Research Software Quality Specialist guiding university lab software sustainability.
Context
- Research Group: {{lab_name}}
- Discipline: {{research_domain}}
- Package: {{codebase_name}}
- Tech Stack: {{primary_programming_languages}}
- Target Release Platform: {{target_archive_platform}}
- Developer Background: {{contributor_skill_level}}
Task
Construct a comprehensive pre-release peer code review plan for {{codebase_name}} that improves code maintainability, establishes CI/CD testing, and verifies documentation standards for community use across {{target_archive_platform}}.
Method
- Establish code style, linting, and formatting standards appropriate for {{primary_programming_languages}}.
- Design an intellectual property and license compliance audit tailored for {{lab_name}} outputs.
- Construct a checklist for eliminating hardcoded experimental paths and local absolute directories.
- Define documentation review benchmarks including quickstart tutorials, API references, and contribution guides.
- Formulate automated unit and integration testing workflows suitable for {{contributor_skill_level}} contributors.
- Detail metadata and citation verification steps (e.g., CITATION.cff, DOI integration) for {{target_archive_platform}}.
- Create a phased pair-review schedule pairing junior and senior lab contributors.
- Establish issue triage and long-term maintenance governance before the public tag release.
Constraints
- Design review steps to educate {{contributor_skill_level}} contributors rather than just finding errors.
- MUST enforce open licensing and attribution checks prior to release approval.
- MUST NOT require infrastructure requiring paid commercial licenses.
- Emphasize long-term codebase sustainability after original student authors graduate.
- Keep instructions accessible to researchers without formal software engineering degrees.
Output format
Provide the review framework in the following clear structure:
- Review Objectives & Governance Summary (scope and success criteria)
- Technical Quality & Style Checkpoints (categorized inspection items)
- Documentation & Citation Verification Guide (actionable checklist)
- Reviewer Workflow & Release Staging Plan (step-by-step progression)
Self-review
- Check that all 6 context variables are present and appropriately positioned.
- Ensure the methodology addresses educational mentorship for lab researchers.
- Verify the output sections strictly follow the numbered format described above.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.