oat-review-receive

To convert markdown code review findings into actionable tasks, you can use a tool to parse the local review artifacts into a normalized findings register and generate a standalone task list. This allows you to triage findings and decide on necessary actions.

Yes, you can triage code review findings from a local markdown file outside of a formal project. This supports ad-hoc triage by auto-detecting or specifying local review files to process findings without altering the main project lifecycle.

The best way to normalize markdown review artifacts into a structured findings register is by parsing the local files to extract and classify findings by severity. This process converts unstructured markdown into a normalized format for triage.

Yes, processing local review artifacts requires file system access. The tool needs this access for artifact location, parsing markdown files into a findings register, and generating the output task lists.

You classify severity and disposition for triaged code review findings through user-driven dispositioning during the artifact normalization process. The tool parses the markdown findings and allows you to assign severity levels to generate actionable tasks.