story-review-loop-cope

Automate three-agent code review for design/story documentation PRs.

1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/gcko/pendulum-of-despair --skill story-review-loop-cope
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: story-review-loop-cope
Source: https://github.com/gcko/pendulum-of-despair/tree/main/.claude/skills/story-review-loop-cope
Command: npx skills add https://github.com/gcko/pendulum-of-despair --skill story-review-loop-cope

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Emulates Copilot's PR review patterns using three specialized agents to identify gaps in story/documentation reviews when Copilot is unavailable, ensuring timely, structured critique for design/PR work.

Core Features & Use Cases

  • Three-agent round (Agent A, B, C) targeting the 10 gap categories from the copilot-gap-taxonomy.
  • Cross-file consistency checks, drift detection, and containment of escalation paths for PR reviews.
  • Use Case: When a story PR requires multi-faceted critique across docs, references, and plans, this skill produces a comprehensive issues report.

Quick Start

Initiate a three-agent Copilot-emulation code-review for a given PR and return a structured issue report.

Frequently Asked Questions about story-review-loop-cope

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

FAQPage Schema
How do I automate multi-agent code review for documentation PRs?

Multi-agent code review for documentation PRs is automated by running a three-agent round that targets gap categories, performs cross-file consistency checks, and executes post-round propagation sweeps to produce a comprehensive issues report.

Can I detect documentation drift across revised docs and references during a PR review?

Documentation drift detection during a PR review is handled by cross-file consistency checks that compare revised docs against references, identifying gaps and containing escalation paths within a structured three-agent emulation report.

What is the best way to perform a structured gap analysis on story documentation?

Structured gap analysis on story documentation applies a copilot-gap-taxonomy across a three-agent round, verifying design and plan consistency while returning a structured critique report for the PR.

Does this work for PRs requiring cross-file consistency checks and escalation containment?

PRs requiring cross-file consistency checks and escalation containment are supported through a round-robin agent collaboration process that executes verification checklists and propagation sweeps to maintain consistency.

How do I emulate Copilot PR review patterns when Copilot is unavailable?

Emulating Copilot PR review patterns when Copilot is unavailable involves deploying three specialized agents to identify gaps, perform drift detection, and generate a structured critique report for design or story work.

When do I need a three-agent round-robin review for my design PRs?

A three-agent round-robin review for design PRs is needed when a story PR requires multi-faceted critique across docs, references, and plans to ensure structured gap analysis and post-round consistency propagation.