ce-code-review

Identify CE code-review violations and suggest remediations for PR gates.

78|15|Updated May 1, 2023
One-click install
npx skills add https://github.com/Moffran/calibrated_explanations --skill ce-code-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-code-review
Source: https://github.com/Moffran/calibrated_explanations/tree/main/.claude/skills/ce-code-review
Command: npx skills add https://github.com/Moffran/calibrated_explanations --skill ce-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CE code reviews ensure changes adhere to calibrated_explanations standards and ADR conformance, reducing regression risk and misalignment with project guidelines.

Core Features & Use Cases

  • Validate module boundaries (ADR-001) to prevent core importing plugins.
  • Enforce lazy imports, future annotations, and numpy-style docstrings.
  • Verify exception handling, fallback visibility, type hints, and deprecation policies to maintain CE-First compliance.

Quick Start

Run a code-review on a pull request to generate a structured violation report.

Frequently Asked Questions about ce-code-review

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

FAQPage Schema
When do I need to validate future annotations and deprecation policies in my code?

Code review for ADR-001 boundary checks validates module boundaries by identifying and reporting violations where core components improperly import plugins, generating a structured report for remediation.

What does CE-First compliance verify in a pull request?

CE-First compliance verification checks exception handling, fallback visibility, type hints, and deprecation policies against calibrated_explanations standards, producing a structured violation report suitable for PR gates.

How do I check numpy-style docstrings and lazy imports in my codebase?

Reviewing numpy-style docstrings and lazy imports involves analyzing your codebase to enforce these coding standards, identifying violations, and suggesting remediations to align with project guidelines.

Can I generate a structured violation report for PR gates from a static analysis review?

Static analysis code review generates a structured violation report covering ADR conformance and CE dimensions like future annotations and exception handling, making it suitable for PR gating.

Does code review for calibrated_explanations standards require any external dependencies?

Code review for calibrated_explanations standards operates with no external dependencies, performing static analysis on your codebase to validate coding standards and ADR conformance natively.

When do I need to validate future annotations and deprecation policies in my code?

Validating future annotations and deprecation policies is needed during code reviews to ensure CE-First compliance, prevent regressions, and maintain alignment with calibrated_explanations project guidelines.