formatting-tribal-review

Define canonical markdown formatting for Tribal review outputs.

9|Updated Feb 11, 2026

Search Tags:#documentation #standardization #output format #review format #tribal

Ready to run

npx skills add https://github.com/samfolo/tribal --skill formatting-tribal-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: formatting-tribal-review
Source: https://github.com/samfolo/tribal/tree/main/.claude/skills/formatting-tribal-review
Command: npx skills add https://github.com/samfolo/tribal --skill formatting-tribal-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that all review outputs from Tribal skills adhere to a strict, consistent, and easily parsable format, improving clarity and automation.

Core Features & Use Cases

Canonical Formatting: Defines the exact structure, section order, and divider rhythm for review outputs.
Reference Conventions: Establishes short-form notation for citing design documents.
Use Case: When a Tribal skill generates a code review, this Skill's format ensures that the verdict, issues, and observations are presented in a predictable way that other systems can reliably process.

Quick Start

Use the formatting-tribal-review skill to ensure your review output conforms to the defined standard.

Frequently Asked Questions about formatting-tribal-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I standardize code review output format for automated processing?▼

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.

What is the canonical structure for Tribal review reporting?▼

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.

How do I format review observations and citations for 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.

Does this review standardization format require any external dependencies?▼

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.

When do I need a standardized output format for code reviews?▼

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.