critique-transcript-analyzer

Analyzes critique transcripts to extract criticisms and suggestions with provenance.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/edri2or/ripo-skills-main --skill critique-transcript-analyzer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: critique-transcript-analyzer
Source: https://github.com/edri2or/ripo-skills-main/tree/main/exported-skills/critique-transcript-analyzer
Command: npx skills add https://github.com/edri2or/ripo-skills-main --skill critique-transcript-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes a critique/review transcript to extract criticisms and actionable suggestions with provenance, enabling traceability to transcript spans and repository references. This skill also validates findings against the codebase, researches potential refinements, and emits an evidence-backed action plan suitable for HITL review.

Core Features & Use Cases

  • Extract criticisms and suggestions with exact transcript provenance.
  • Validate findings against repository state and locate relevant code references.
  • Research refinements using external sources and produce targeted recommendations.
  • Generate a grounded action plan with explicit provenance for each recommendation.
  • Ideal for architecture/code review transcripts and design critique sessions.

Quick Start

Provide a critique transcript and let this skill generate a structured, evidence-backed action plan with provenance.

Frequently Asked Questions about critique-transcript-analyzer

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

FAQPage Schema
How do I extract actionable suggestions from an architecture review transcript?

Extracting actionable suggestions from a review transcript involves analyzing the critique text to identify criticisms with exact provenance, validating findings against the codebase, and generating an evidence-backed action plan.

What is transcript provenance and why is it needed for code reviews?

Transcript provenance links extracted criticisms and suggestions to exact spans in the review dialogue, ensuring traceability and evidence-backed validation against repository references before generating an action plan.

How do I validate code review criticisms against my repository state?

Validating code review criticisms against your repository state requires cross-referencing extracted transcript findings with actual repo references to confirm traceability and produce a grounded action plan for HITL approval.

Can I research refinements for suggestions extracted from a design critique session?

Yes, researching refinements for suggestions extracted from a design critique session involves using external sources to investigate targeted recommendations and produce an evidence-backed action plan with explicit provenance.

Does generating an evidence-backed action plan require human-in-the-loop approval?

Generating an evidence-backed action plan includes an explicit HITL gate, meaning a human must review and approve the validated findings and recommendations before the plan is finalized.