factory-code-review

Score code compliance against acceptance criteria and classify issues by severity.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/JongHyunLee84/factory --skill factory-code-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: factory-code-review
Source: https://github.com/JongHyunLee84/factory/tree/main/skills/factory-code-review
Command: npx skills add https://github.com/JongHyunLee84/factory --skill factory-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the code review process by providing quantitative scoring against acceptance criteria, classifying issues by severity, and delivering a clear verdict on code readiness for deployment.

Core Features & Use Cases

  • Quantitative Scoring: Measures code compliance against defined acceptance criteria, moving beyond subjective feedback.
  • Severity Classification: Categorizes issues into Critical, Important, and Minor for prioritized action.
  • Automated Verdict: Provides a PASS, NEEDS IMPROVEMENT, or REDESIGN verdict based on compliance score.
  • Use Case: A development team uses this Skill after a feature is implemented to get an objective assessment of code quality and adherence to requirements before merging to the main branch.

Quick Start

Use the factory-code-review skill to review the latest code changes against the acceptance criteria defined in the project's architect documentation.

Frequently Asked Questions about factory-code-review

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

FAQPage Schema
How do I automate quantitative code review against acceptance criteria?

Automated code review performs quantitative scoring against acceptance criteria by analyzing Git SHA changes. It classifies deviations by severity and measures compliance to provide objective quality assessments before deployment.

What is severity classification in automated code compliance checks?

Severity classification in code compliance categorizes deviations into Critical, Important, and Minor issues. This prioritized action approach helps development teams address severe deviations first before merging.

How do I get a pass fail verdict for code readiness before merging?

Code readiness verdicts use compliance scores to output PASS, NEEDS IMPROVEMENT, or REDESIGN. The verdict recommends routing to development or architecture workflows based on measured compliance.

Can I use Git SHA to identify scope for code review automation?

Git SHA identifies scope for code review automation by analyzing specific code changes. The review scores implementation against predefined requirements and classifies deviations to determine readiness.

What are the limitations of quantitative code review scoring?

Quantitative code review scoring is limited to evaluating implementation against predefined acceptance criteria. It focuses on objective compliance measurement and severity classification rather than subjective feedback.