New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

WebRTC HTA-Style Code Review

by webrtc-sdk in webrtc-sdk/webrtc

Reviews WebRTC changes through one senior engineer's lens: process hygiene, API stability, spec compliance, thread safety and modern C++, with feedback tuned to internal or external authors.

BSD-3-ClauseAuto-check passedDevelopment

Install WebRTC HTA-Style Code Review

skills CLI
$ npx skills add webrtc-sdk/webrtc --skill hta-reviewer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install webrtc-sdk/webrtc hta-reviewer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/webrtc-sdk/webrtc.git skills-src && mkdir -p .claude/skills && cp -r skills-src/agents/skills/hta-reviewer .claude/skills/hta-reviewer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
hta-reviewer
GitHub stars
446
Used in
1 other repo
Token cost
~754 tokens
SKILL.md length
342 words
Files
3 (incl. references)
Skills in repo
6
Repo updated
First seen
Licence
BSD-3-Clause

At a glance

Reviews WebRTC changes through one senior engineer's lens: process hygiene, API stability, spec compliance, thread safety and modern C++, with feedback tuned to internal or external authors.

  • Works in 3 steps: Process Hygiene → Architectural Guardrails → Technical Standards
  • Reviewing a WebRTC change before it lands
  • SKILL.md covers Core Mandates, Workflow and Tone and Style
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

The skill adopts the reviewer's lens of Harald Alvestrand and gives direct, technical, process-minded feedback. Process hygiene covers rebasing on the tip of tree, flagging obsolete symbols such as anything in the `rtc::` namespace, requiring relands to explain why they are safe, a `Bug:` line on every change, and real deletion instead of commented-out code. Architecture rules treat new public APIs under `api/` as expensive, needing default implementations, and prefer dependency injection to test-mode flags in production code.

Technical standards include cross-checking logic against W3C and IETF specifications, hunting for missing `RTC_GUARDED_BY`, `RTC_DCHECK_RUN_ON` and `SequenceChecker` use, and modern C++ habits such as `nullptr`, `absl::string_view`, `std::span` and the `webrtc::Timestamp` and `TimeDelta` types. The workflow checks the author's email first: internal authors get architecture and threading feedback, while external ones also get process onboarding on the CLA, AUTHORS and Bug format. It then reads the diff and works through `references/checklist.md` and `references/bad_patterns.md`.

When your agent uses it

  • Reviewing a WebRTC change before it lands
  • Checking a patch for thread-safety annotations and sequence checks
  • Giving a first-time external contributor process and style feedback

Example prompts

  • “Review this WebRTC change in the HTA style and focus on thread safety.”
  • “Check whether this CL adds a public API without default implementations.”
  • “Give feedback on this patch from an external contributor, including the process steps.”

Requirements

  • A WebRTC change (CL) or diff to review

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Process Hygiene
  2. Architectural Guardrails
  3. Technical Standards

What it can do on your machine

Read from SKILL.md and the folder at commit 67c4578. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

WebRTC HTA-Style Code Review loads about 754 tokens when it runs, and up to ~2.3k if it reads all its reference files. Until then it costs about 53 tokens; SKILL.md has 342 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~53
When it runs · the whole SKILL.md, loaded when a task matches
~754
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from webrtc-sdk/webrtc at commit 67c4578, republished under its BSD-3-Clause licence (© webrtc-sdk). 342 words, ~754 tokens.

Download SKILL.mdSave it as .claude/skills/hta-reviewer/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
hta-reviewer
description
Automated code review following Harald Alvestrand's (hta@) standards for WebRTC. Use this skill to analyze CLs for thread safety, process hygiene, architectural robustness, and modern C++ adoption.

HTA Reviewer Skill

This skill adopts the "Reviewer's Lens" of Harald Alvestrand, a senior WebRTC engineer. It provides direct, technical, and process-oriented feedback on code changes.

Core Mandates

1. Process Hygiene
  • Freshness: Ensure the CL is rebased against the tip of tree. Flag usage of obsolete symbols (e.g., anything in the rtc:: namespace).
  • Documentation: Relands MUST explain why they are now safe. Every CL should have a Bug: line (e.g., webrtc:XXXX or Bug: None).
  • Completeness: "Delete" means remove the code, not comment it out. No trailing spaces.
2. Architectural Guardrails
  • API Stability: New public APIs (in the `api/` directory) are "expensive." They must include default implementations and markers for pure virtuals to prevent breaking downstream (internal) builds.
  • Testing: Dislike "test mode" flags in production code. Prefer dependency injection or dedicated perf-test binaries over adding command-line flags to unittests.
3. Technical Standards

  • Spec Compliance: WebRTC logic is governed by standards. Always cross-reference logic with relevant W3C (WebRTC-PC) and IETF (RFCs) specifications. Flag arbitrary logic that contradicts these standards.

  • Thread Safety: Aggressively check for RTC_GUARDED_BY, RTC_DCHECK_RUN_ON, and proper use of SequenceChecker.

  • Modern C++:

    • Use nullptr (never NULL).
    • Prefer absl::string_view over std::string_view.
    • Use std::span for array views.
    • Use webrtc::Timestamp and webrtc::TimeDelta instead of raw integers for time.

  • Naming: Method names must be descriptive; boolean-returning methods should be phrased as questions (e.g., IsFoo() or HasBar()).

Workflow

  1. Analyze the Contributor: Check the author's email.
    • Internal (@google.com, @webrtc.org, @chromium.org): Focus on high-level architecture, thread safety, and project migrations. Skip onboarding formalities.
    • External (Everyone else): Provide all technical feedback AND mandatory process onboarding (CLA, AUTHORS, Bug format). Be pedagogical but firm on hygiene.
  2. Analyze the Change: Read the diff and understand the intent.
  3. Run the Checklist: Consult checklist.md.
  4. Identify Bad Patterns: Look for "Bad Ideas" in bad_patterns.md.
  5. Provide Feedback: Use a direct, technical tone. For externals, start with a "Process & Formalities" section.

Tone and Style

  • Direct: Avoid fluff. If a fix isn't applied, say "Not fixed."
  • Senior: Focus on long-term maintainability and downstream impact.
  • Strict: Do not ignore presubmit errors or lack of tests.

© webrtc-sdk, BSD-3-Clause. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in agents/skills/hta-reviewer of webrtc-sdk/webrtc.

  • SKILL.md
  • references/bad_patterns.md
  • references/checklist.md

Open the folder on GitHubat commit 67c4578

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in webrtc-sdk/webrtc, which our catalogue first saw on October 7, 2026.

Compare with similar skills

WebRTC HTA-Style Code Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

WebRTC HTA-Style Code Review compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
WebRTC HTA-Style Code Review this skillwebrtc-sdk/webrtc4461 repos~754Automated safety check: PassBSD-3-Clause
Qt C++ Code Reviewx-tools-author/x-tools1.1k2 repos~4.3kAutomated safety check: PassBSD-3-Clause
Code Review Excellenceandrew-yangy/gru-ai155—~1.7kAutomated safety check: NotesMIT
Code Revieweralirezarezvani/claude-skills28k1 repos~1.6kAutomated safety check: PassMIT
WooCommerce Code Reviewwoocommerce/woocommerce11k3 repos~1.1kAutomated safety check: PassCustom licence
Skill Doli Code ReviewDolibarr/dolibarr7.7k1 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • Qt C++ Code Review

    x-tools-author/x-tools

    Read-only review of Qt6 C++ code that combines a deterministic lint script with six parallel analysis agents and reports only high-confidence issues.

    1.1k GitHub starsUsed in 2 repos~4.3k tokens
    DevelopmentAuto-check passed

  • Code Review Excellence

    andrew-yangy/gru-ai

    Provides comprehensive code review guidance for React 19, Vue 3, Rust, TypeScript, Java, Python, and C/C++.

    155 GitHub stars~1.7k tokensUpdated 7 mo ago
    DevelopmentAuto-check: notes

  • Code Reviewer

    alirezarezvani/claude-skills

    Code review automation for TypeScript, JavaScript, Python, Go, Swift, Kotlin, C, .NET, Java, C, C++, Rust, Ruby, PHP, and Dart/Flutter.

    28k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed

  • WooCommerce Code Review

    woocommerce/woocommerce

    Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.

    11k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Skill Doli Code Review

    Dolibarr/dolibarr

    Reviews Dolibarr PHP code for compliance with coding standards and security best practices, and fixes identified issues.

    7.7k GitHub starsUsed in 1 repo~1.1k tokens
    DevelopmentAuto-check passed

  • Dignified Python Standards

    docling-project/docling

    Applies opinionated production Python conventions chosen by the project's Python version: modern type syntax, pathlib, explicit checks and interface guidance.

    69k GitHub stars~1.5k tokensUpdated today
    DevelopmentAuto-check passed

More from webrtc-sdk/webrtc

  • GN Check Autofix

    webrtc-sdk/webrtc

    Fixes GN dependency errors in WebRTC BUILD.gn files with the gn_check_autofix.py script, including missing deps and misused rtc_source_set targets.

    446 GitHub starsUsed in 1 repo~605 tokens
    Auto-check passed

  • gtest-parallel Test Runner

    webrtc-sdk/webrtc

    Runs Google Test binaries in parallel with gtest-parallel to speed up single-threaded tests, repeat flaky ones and filter specific tests.

    446 GitHub starsUsed in 1 repo~432 tokens
    Auto-check passed

  • WebRTC Include Cleaner

    webrtc-sdk/webrtc

    Runs the WebRTC include-cleaner tool to add missing and remove unused C++ include directives before uploading a CL or after refactoring.

    446 GitHub starsUsed in 1 repo~545 tokens
    Auto-check passed

  • WebRTC Changelog Generator

    webrtc-sdk/webrtc

    Builds a categorized HTML changelog for a WebRTC release from the git log between two branch heads, with a summary and commit and review links.

    446 GitHub starsUsed in 1 repo~485 tokens
    Auto-check passed

  • Git CL for Gerrit

    webrtc-sdk/webrtc

    Provides commands for interacting with Gerrit CLs using git cl, including issue management and non-interactive uploads.

    446 GitHub starsUsed in 1 repo~146 tokens
    Auto-check passed

Works with

Categories

Questions about WebRTC HTA-Style Code Review

What does WebRTC HTA-Style Code Review do?

Reviews WebRTC changes through one senior engineer's lens: process hygiene, API stability, spec compliance, thread safety and modern C++, with feedback tuned to internal or external authors. The skill adopts the reviewer's lens of Harald Alvestrand and gives direct, technical, process-minded feedback. Process hygiene covers rebasing on the tip of tree, flagging obsolete symbols such as anything in the `rtc::` namespace, requiring relands to explain why they are safe, a `Bug:` line on every change, and real deletion instead of commented-out code.

When should I use WebRTC HTA-Style Code Review?

WebRTC HTA-Style Code Review fits situations like: reviewing a WebRTC change before it lands; checking a patch for thread-safety annotations and sequence checks; giving a first-time external contributor process and style feedback.

How do I install WebRTC HTA-Style Code Review in Claude Code?

Run `npx skills add webrtc-sdk/webrtc --skill hta-reviewer -a claude-code`. Or copy the skill folder (agents/skills/hta-reviewer in webrtc-sdk/webrtc) into .claude/skills/hta-reviewer in your project. Claude Code loads it when a task matches its description.

How do I install WebRTC HTA-Style Code Review in Codex?

Run `npx skills add webrtc-sdk/webrtc --skill hta-reviewer -a codex`. Or copy the skill folder (agents/skills/hta-reviewer in webrtc-sdk/webrtc) into .agents/skills/hta-reviewer in your project. Codex loads it when a task matches its description.

Can I use WebRTC HTA-Style Code Review in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add webrtc-sdk/webrtc --skill hta-reviewer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/hta-reviewer, .gemini/skills/hta-reviewer, .github/skills/hta-reviewer and .opencode/skills/hta-reviewer in your project.

What does WebRTC HTA-Style Code Review need to run?

SKILL.md names no scripts, command-line tools or credentials: WebRTC HTA-Style Code Review is instructions for the agent only. Our summary lists: A WebRTC change (CL) or diff to review.

Does WebRTC HTA-Style Code Review access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is WebRTC HTA-Style Code Review safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does WebRTC HTA-Style Code Review use?

WebRTC HTA-Style Code Review is published under the BSD-3-Clause licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does WebRTC HTA-Style Code Review use?

About 754 tokens (SKILL.md is roughly 3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.5k tokens, read only when the agent opens those files.

What are the alternatives to WebRTC HTA-Style Code Review?

Skills that share tags, products or a category with WebRTC HTA-Style Code Review: Qt C++ Code Review (x-tools-author/x-tools, 1.1k stars), Code Review Excellence (andrew-yangy/gru-ai, 155 stars), Code Reviewer (alirezarezvani/claude-skills, 28k stars) and WooCommerce Code Review (woocommerce/woocommerce, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains WebRTC HTA-Style Code Review?

webrtc-sdk (a GitHub organization) maintains it in webrtc-sdk/webrtc, which has 446 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 6, 2026.

Source: webrtc-sdk/webrtc on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.