ably-review

Analyze current branch changes against Ably command conventions using LSP and grep checks.

5|Updated Mar 24, 2025

Search Tags:#conventions #lsp #grep #branch #static-analysis #code-review

Ready to run

npx skills add https://github.com/ably/ably-cli --skill ably-review

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review current branch changes against the conventions defined in the ably-new-command skill, enabling fast, focused pre-PR checks and preventing drift from established patterns. It uses a hybrid approach combining LSP-based structural analysis with grep/read textual checks to verify the changes on the branch.

Core Features & Use Cases

LSP-powered analysis: goToDefinition, hover, documentSymbol provide type and structure awareness for changed commands.
Text-pattern checks: grep/read-based validations for error handling, camelCase usage, and formatting consistency.
Scope-focused reviews: analyzes only the current branch versus main, making PR reviews faster and more targeted.

Quick Start

Run ably-review to compare your current branch against main and validate it against the ably-new-command conventions.

Frequently Asked Questions about ably-review

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

FAQPage Schema

How do I review code changes on my branch against coding conventions before a PR?▼

To review code changes against coding conventions before a PR, analyze your current branch against the main branch using LSP structural checks and textual grep validations. This hybrid approach identifies deviations from established patterns to ensure fast, targeted pre-PR readiness.

What is the best way to validate command conventions in modified code files?▼

Validating command conventions in modified code files is best achieved through a hybrid approach using LSP-based structural analysis for type awareness and grep/read textual checks for error handling and formatting. This ensures fast, focused conformance verification.

How does LSP-based static analysis work for branch code reviews?▼

LSP-based static analysis for branch code reviews works by using features like goToDefinition, hover, and documentSymbol to provide type and structure awareness for changed commands, verifying conformance against established command conventions efficiently.

Can I use grep and read commands to check error handling and formatting consistency?▼

Yes, you can use grep and read commands to perform text-pattern checks for error handling, camelCase usage, and formatting consistency. These textual validations complement LSP structural analysis to verify code changes comprehensively.

Why should I scope static analysis to only changes since the main branch?▼

Scoping static analysis to only changes since the main branch makes pre-PR code reviews faster and more targeted. It focuses exclusively on your deviations and improvement opportunities rather than analyzing the entire codebase.