Enforce naming and API-design hygiene for Pinot's public surface.
npx skills add https://github.com/apache/pinot --skill review-naming-api
Please help me install this Agent Skill. Skill: review-naming-api Source: https://github.com/apache/pinot/tree/main/.claude/skills/review-naming-api Command: npx skills add https://github.com/apache/pinot --skill review-naming-api
Review and enforce naming and API-design hygiene for Pinot's public surface, catching inconsistencies before they reach production.
Review the latest pull request diff focusing on public API names, REST field names, and Javadoc coverage to enforce naming and API-design hygiene.
High-intent search queries and answers about installing and using this skill.
To enforce public API naming consistency during code reviews, analyze pull request diffs to detect inconsistent public API names, SPI methods, and REST fields. This ensures new public classes follow established naming conventions and API design hygiene.
Checking Javadoc coverage on new public classes involves scanning pull request diffs to verify that all newly introduced public APIs have Javadoc. It also ensures inline fully-qualified class names are avoided to maintain clean code.
Public API design hygiene for REST endpoints and JSON fields is the practice of maintaining consistent naming conventions and avoiding inline FQCNs across the public surface. It prevents inconsistencies from reaching production by enforcing standards during PR reviews.
Yes, you can use automated checks to detect inconsistent SPI method names in code diffs. By focusing on the public surface of a project, these checks provide actionable guidance to enforce naming hygiene before changes are merged.
The best way to avoid inline fully-qualified class names in public APIs is to review code diffs for the public surface and enforce API design hygiene rules. This catches FQCN usage and ensures consistent naming before production deployment.
LaiTszKinPrepare review-ready pull requests with standardized branch naming and structured English PR bodies.
baekenoughAnalyze pull requests to generate targeted code-quality improvement reports.
HomericIntelligenceDetect code smells and complexity issues in codebases.
ekremmkasapEnforce Python code style with ruff, mypy, and Google-style docstrings.
