formatting-tribal-review

To standardize code review output format, you apply a canonical structure that defines exact section order, divider rhythm, and markdown formatting, ensuring the review verdict and issues remain consistent and easily parsable by other systems.

The canonical structure for Tribal review reporting is a strict markdown format that defines section inclusion rules, divider rhythm, and short-form reference notation for citing design documents to guarantee machine readability.

You format review observations and citations by adhering to established short-form notation for design document references and applying specific markdown section inclusion rules, ensuring predictable output for automated processing.

No, this review standardization format requires no external dependencies, functioning purely as a formatting standard to structure review outputs, section order, and citation conventions within the Tribal system.

You need a standardized output format for code reviews when your Tribal skills generate reports that require automated processing, ensuring clarity and consistency across verdicts, issues, and observations for downstream systems.