research-algorithm-checker

Trace research code flow and validate edge cases and numerical correctness.

Updated May 13, 2026
One-click install
npx skills add https://github.com/Ricardo-Vae/codex-research-skills --skill research-algorithm-checker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: research-algorithm-checker
Source: https://github.com/Ricardo-Vae/codex-research-skills/tree/main/skills/research-algorithm-checker
Command: npx skills add https://github.com/Ricardo-Vae/codex-research-skills --skill research-algorithm-checker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps researchers rigorously verify that target code implements the intended research algorithm correctly, catching bugs, logic mismatches, numerical mistakes, boundary issues, and efficiency problems before they waste more training or experiment cycles.

Core Features & Use Cases

  • Step-by-step algorithm walkthrough: Traces the algorithm from entry to outputs, confirming each transformation against the expected design.
  • Boundary, shape, dtype, and edge-case analysis: Checks for indexing errors, null/empty handling, tensor shape/dtype mismatches, and other failure points.
  • Numerical and computation correctness checks: Validates mathematical implementations (loss/probabilities/thresholds/gradient flow) for correctness.
  • Performance and efficiency review: Identifies wasted computation, memory inefficiency, and cache/parallelization opportunities.
  • Design-to-implementation consistency validation: Compares code against papers/notes/pseudocode to pinpoint deviations.
  • Issue tracking with deduplication: Uses ISSUES.md to track todo/doing/done/discard so discarded optimization ideas are not repeated.

Quick Start

Use the research-algorithm-checker skill only when you can provide the exact trigger phrase “科研启动-检查”, then tell it which repository files/functions you want reviewed and what reference (paper/pseudocode/design) to align with.

Frequently Asked Questions about research-algorithm-checker

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

FAQPage Schema
How do I verify machine learning algorithm correctness in my research code?

To verify machine learning algorithm correctness, you can use a multi-agent review workflow that traces code flow from entry to outputs, validates edge cases, and checks numerical logic against your reference design. This process categorizes bugs and optimization findings for academic R&D.

What is the best way to check numerical correctness in loss and probability logic?

Checking numerical correctness in loss and probability logic involves validating mathematical implementations for thresholds and gradient flow. A dedicated algorithm checker compares your code against papers or pseudocode to pinpoint deviations and identify computation mistakes.

How do I trace tensor shape and dtype mismatches during model debugging?

Tracing tensor shape and dtype mismatches requires boundary and edge-case analysis that checks for indexing errors and null handling. An algorithm verification workflow systematically reviews these failure points to ensure your training pipeline runs correctly.

Does algorithm code review help find performance optimization opportunities?

Algorithm code review does help find performance optimization opportunities by identifying wasted computation, memory inefficiency, and cache or parallelization opportunities. It ensures your research code is both correct and efficient before running experiment cycles.

How do I track and deduplicate bugs found during research code verification?

To track and deduplicate bugs found during research code verification, use an ISSUES.md file with todo, doing, done, and discard statuses. This issue tracking method ensures discarded optimization ideas are not repeated during the algorithm review workflow.

Do I need to provide a reference paper to check my training pipeline implementation?

You do need to provide a reference paper, pseudocode, or design document to check your training pipeline implementation. Design-to-implementation consistency validation requires comparing your code against these references to pinpoint exact deviations.