safer-docs-reader

Aggregate four haiku sub-agent verdicts into a severity-weighted SHIP or REVISE decision.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/chughtapan/safer-by-default --skill safer-docs-reader
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: safer-docs-reader
Source: https://github.com/chughtapan/safer-by-default/tree/main/skills/safer-docs-reader
Command: npx skills add https://github.com/chughtapan/safer-by-default --skill safer-docs-reader

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cold-start auditing of a docs artifact (GitHub issue/PR body or local markdown) by orchestrating four haiku personas to produce a structured verdict and prevent context leakage, ensuring consistent review quality.

Core Features & Use Cases

  • Ephemeral orchestration: creates a temporary Team and four haiku sub-agents to read the artifact cold.
  • Structured verdicts: collects per-persona judgments and aggregates them via a severity-weighted consensus.
  • Artifact publication: posts the aggregate report back to the artifact's thread or stdout for local files.
  • Round-limited workflow: supports up to 3 rounds with explicit gating for round 3.

Quick Start

Use the skill against an artifact (issue, PR, or file) to trigger the full three-round review and publish the aggregate report.

Frequently Asked Questions about safer-docs-reader

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

FAQPage Schema
How do I automate GitHub PR review using multiple AI agents?

Automate GitHub PR review by spawning an ephemeral team of four haiku sub-agents that read the artifact cold. The orchestrator collects their per-persona judgments, aggregates them via severity-weighted consensus, and posts the final SHIP or REVISE verdict back to the PR thread.

What is multi-agent orchestration for documentation auditing?

Multi-agent documentation auditing is a process where multiple haiku sub-agents evaluate a docs artifact cold. This approach prevents context leakage and ensures consistent review quality by aggregating individual structured verdicts through a severity-weighted consensus mechanism.

Can I review local markdown files with an automated AI agent workflow?

You can review local markdown files by resolving the file into a deterministic input for evaluation. The workflow evaluates the content across three rounds and publishes the final aggregated SHIP or REVISE report directly to standard output.

How does severity-weighted consensus work for AI issue review?

Severity-weighted consensus for AI issue review works by collecting structured verdicts from four haiku sub-agents. The orchestrator weighs the severity of each identified issue to decide a final SHIP or REVISE outcome, ensuring consistent review quality without context leakage.

Do I need gh CLI authentication to run automated AI docs review?

You need gh CLI authentication to run automated AI docs review on GitHub artifacts. The workflow requires gh CLI access to resolve issue and PR bodies, alongside ephemeral TeamCreate and Agent tools to spawn the sub-agents.

What are the limitations of round-limited multi-agent artifact review?

The limitation of this multi-agent artifact review is a strict round limit of three rounds with explicit gating for round three. This constraint ensures deterministic evaluation but prevents extended iterative refinement beyond the third round.