research-reviewer

To ensure technical research documents remain objective, you can review them against strict documentation standards that filter out subjective language and verify all claims describe existing code without proposing solutions.

Verifying evidence and completeness in code analysis research requires checking that all findings include specific file:line references and flagging missing schema details or unaddressed aspects of the original research question.

You can review a research document for missing file:line references by evaluating it against evidence-based reporting rules that require precise code pointers to back up every technical claim made in the text.

Yes, you can enforce documentation standards on technical writing by running the document through a structured review process that generates a report identifying subjective opinions and gaps in the research.

Yes, the research review process flags gaps in technical documentation by assessing completeness and identifying missing details or unaddressed aspects of the original research question during the evaluation.

The structured review report evaluates research and saves the output to a specific file path, validating objectivity and evidence before generating the final assessment of the document.