review-logic

Compare code implementations against design documents and generate audit reports.

1|Updated Dec 22, 2025
One-click install
npx skills add https://github.com/Harries/hydpromptkit --skill review-logic-harries
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-logic
Source: https://github.com/Harries/hydpromptkit/tree/main/skills/review-logic
Command: npx skills add https://github.com/Harries/hydpromptkit --skill review-logic-harries

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

设计与实现的一致性校验,帮助开发团队确认代码实现是否严格遵循设计文档,避免实现偏离与功能错位。

Core Features & Use Cases

  • 设计对齐检查:对比设计文档与实现的关键设计点,输出偏差点清单。
  • 变更追踪与回溯:在变更后快速重新验证设计一致性,支持回溯分析。
  • 适用场景:适用于单元、集成与模块级的设计一致性验证,提升代码质量与可维护性。

Quick Start

让用户提供设计文档路径和需要对比的代码,生成完整的对照分析报告。

Frequently Asked Questions about review-logic

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

FAQPage Schema
How do I check code implementation against design documents?

To check code implementation against design documents, you provide the design file path and source code to extract inputs, parse logic flows, and generate a structured audit report detailing alignment deviations.

What is design-implementation consistency validation?

Design-implementation consistency validation is the process of comparing code logic flows against design artifacts to confirm strict adherence, preventing functional misalignment and implementation drift in software engineering projects.

Can I use design validation for unit and integration level checks?

Yes, you can use design validation for unit, integration, and module-level checks. The process extracts inputs from requirement documents and code to perform logic flow comparisons and output an audit-ready report.

How do I track design alignment after code changes?

To track design alignment after code changes, you run a rapid re-validation by re-parsing the updated code against existing design artifacts, generating a new deviation checklist for retrospective analysis.

Do I need explicit requirement documents to perform a logic review?

Yes, explicit requirement documents and design artifacts are required. The logic review mechanism parses these files to extract design points and compare them directly with the implemented code logic flows.

What is the best way to generate an audit-ready report for code review?

The best way to generate an audit-ready report for code review is to automate the comparison of design documents with code implementations, systematically extracting and parsing logic flows to output a structured deviation list.