simplify-ceda

Review R and Python code diffs against CEDA standards for reuse and quality.

Updated Nov 8, 2024
One-click install
npx skills add https://github.com/cedanl/.github --skill simplify-ceda
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: simplify-ceda
Source: https://github.com/cedanl/.github/tree/main/.claude/skills/simplify-ceda
Command: npx skills add https://github.com/cedanl/.github --skill simplify-ceda

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review changed code for reuse, quality, and efficiency against CEDA standards. Fix any issues found. Use after writing or editing code in cedanl repositories.

Core Features & Use Cases

  • Identify duplicates and opportunities for reuse across R and Python changes.
  • Enforce CEDA-aligned quality checks during review and cleanup.
  • Provide actionable guidance to fix and refactor code efficiently.

Quick Start

Execute the three-agent review workflow on the diff of your latest commit to surface reuse opportunities and quality improvements.

Frequently Asked Questions about simplify-ceda

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

FAQPage Schema
How do I review code diffs for reuse opportunities and quality issues?

To review code diffs for reuse and quality, run a parallel three-agent workflow that surfaces duplicates, quality issues, and refactoring opportunities against CEDA standards across changed R, Python, or mixed-language files.

What is static analysis for CEDA standards in R and Python repositories?

Static analysis for CEDA standards identifies and fixes code issues in changed R and Python files to improve reuse, quality, and efficiency, providing actionable guidance to refactor and clean up code.

Can I use automated refactoring on mixed-language R and Python codebases?

Yes, automated refactoring can be applied to mixed-language R and Python codebases by operating on changed files within the diff to identify duplicates and enforce CEDA-aligned quality checks across both languages.

What's the best way to enforce quality assurance checks after editing code?

The best way to enforce quality assurance is to execute a three-agent review workflow on your latest commit diff to surface quality improvements, reuse opportunities, and potential refactors aligned with CEDA standards.

Why do I need a root SKILL.md file for code review automation?

A root SKILL.md file is required because validation checks ensure the skill structure includes a name and description, and it guides automation steps to validate dependencies, components, and safety considerations.

Does the three-agent review workflow fix issues automatically or only surface them?

The three-agent review workflow both surfaces and fixes code issues found in diffs, providing actionable guidance to resolve duplicates, quality issues, and potential refactors efficiently against CEDA standards.