code-review-demos

Audit demo applications for API drift and stale example code.

5|Updated Mar 24, 2026

Search Tags:#code review #e2e tests #sdk #playwright #demos #api drift

Ready to run

npx skills add https://github.com/ably/ably-ai-transport-js --skill code-review-demos

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review-demos
Source: https://github.com/ably/ably-ai-transport-js/tree/main/.claude/skills/code-review-demos
Command: npx skills add https://github.com/ably/ably-ai-transport-js --skill code-review-demos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill audits repository demos against code changes so you can catch stale API usage, broken examples, and missing test coverage before users rely on them.

Core Features & Use Cases

Checks whether demo code still imports and calls changed public APIs correctly.
Flags stale patterns, renamed or removed symbols, and outdated references in demo documentation or comments.
Reviews demo Playwright e2e coverage to ensure changed flows remain exercised.
Use it when SDK or library changes may require updates to sample apps, demo wiring, or test assertions.

Quick Start

Ask this skill to review the repository's demos for API drift and e2e coverage against the latest change.

Frequently Asked Questions about code-review-demos

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

FAQPage Schema

How do I check for API drift in my SDK demo applications?▼

You can check for API drift in SDK demo applications by auditing demo folders and sample apps against changed public APIs to verify imports, calls, and documentation references for renamed or removed symbols.

What is stale demo code and how does it affect SDK sample apps?▼

Stale demo code occurs when sample apps contain outdated API calls, renamed symbols, or removed references after library changes. Auditing demos catches these broken examples and missing test coverage before release.

How do I keep Playwright e2e tests current with API changes?▼

To keep Playwright e2e tests current with API changes, review the test suites against modified public APIs to ensure changed runtime behavior and option shapes remain exercised and assertions match updated entry points.

Can I use this to review demo documentation references for removed APIs?▼

Yes, you can review demo documentation and comments to flag outdated references to renamed or removed symbols, ensuring that documentation examples align correctly with the latest signature-changed public APIs.

Does this skill modify demo code when it finds outdated API usage?▼

No, this skill does not modify demo code when it finds outdated API usage. It produces a read-only conformance report verifying imports, calls, and test coverage against signature-changed APIs.