dev-audio-review

Review audio-lesson code, tests, and documentation across three phases.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/code-review-benchmark/coderabbit_prs2__forge-gpu__coderabbit__PR323__20260317 --skill dev-audio-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-audio-review
Source: https://github.com/code-review-benchmark/coderabbit_prs2__forge-gpu__coderabbit__PR323__20260317/tree/main/.claude/skills/dev-audio-review
Command: npx skills add https://github.com/code-review-benchmark/coderabbit_prs2__forge-gpu__coderabbit__PR323__20260317 --skill dev-audio-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, multi-phase review of audio-lesson implementations to improve code correctness, documentation quality, and test robustness before the final development pass.

Core Features & Use Cases

  • Phase-driven review: Code correctness, parameter validation, thread safety, resource cleanup, and testing across audio-related modules.
  • Verification checks: Ensures rendering baselines, UI integration, and audio baselines across lessons; enforces a repeatable QA loop with fixes and revalidations.
  • Documentation compliance: Verifies inline documentation, readme accuracy, and cross-reference alignment with code.

Quick Start

Run the multi-phase audio-review on a lesson directory to identify issues and drive fixes in three passes.

Frequently Asked Questions about dev-audio-review

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

FAQPage Schema
How do I review audio lesson code for correctness and thread safety?

You review audio lesson code by applying phase-based checks for correctness, parameter validation, thread safety, and resource cleanup across modules. This structured process identifies rendering and UI integration issues while enforcing audio baselines.

What is a multi-phase code review for audio lessons?

A multi-phase audio lesson review is a three-pass process evaluating code, headers, tests, and documentation. It enforces lesson contract verification, UI rendering baselines, and documentation auditing to achieve comprehensive quality assurance.

How do I verify documentation compliance for audio lesson modules?

You verify documentation compliance by auditing inline documentation, readme accuracy, and cross-reference alignment with code. This documentation auditing phase ensures all references match the implementation across audio lessons.

Can I use an automated QA loop to fix audio rendering and test issues?

Yes, you can use a repeatable QA loop to validate, fix, and revalidate audio rendering and test issues. This automated process drives issue resolution in three passes to ensure UI baselines and testing requirements are met.

Does audio lesson review require dependencies or external components?

No, audio lesson review requires no external dependencies or components. It operates as a standalone, advanced implementation that runs directly on a lesson directory to execute specialized phase-based checks.