arn-code-review-implementation

Compare implemented code against project plans and report structured findings.

31|3|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/AppsVortex/arness --skill arn-code-review-implementation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: arn-code-review-implementation
Source: https://github.com/AppsVortex/arness/tree/main/plugins/arn-code/skills/arn-code-review-implementation
Command: npx skills add https://github.com/AppsVortex/arness --skill arn-code-review-implementation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams ensure that a completed implementation matches the project plan, code patterns, and testing standards, surfacing discrepancies as structured artifacts.

Core Features & Use Cases

  • Post-execution quality gate that compares implementation artifacts against the plan, reports ERRORS, WARNINGS, and INFO with a final verdict across multiple checks (plan compliance, pattern compliance, and testing coverage).
  • Supports cross-layer and visual-testing options when configured, and generates actionable findings that guide remediations before shipping.
  • Useful after arn-code-execute-plan in multi-phase projects to validate features, tests, and architecture conformance, with artifacts stored for traceability.

Quick Start

Run the implementation review after completing arn-code-execute-plan to generate a structured report of findings and a final verdict.

Frequently Asked Questions about arn-code-review-implementation

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

FAQPage Schema
How do I verify code implementation matches the project plan and patterns?

Code review after implementation requires comparing completed artifacts against the project plan and stored patterns. This skill reads reports, plans, and pattern documents to identify deviations and output structured findings with severities plus a final verdict.

How does an automated quality gate check pattern compliance and testing coverage?

An automated quality gate checks pattern compliance by reading stored code and testing patterns, then comparing them against implemented artifacts. It assesses plan compliance, pattern adherence, and artifact quality to generate actionable findings before shipping.

What is the best way to surface discrepancies between implemented code and testing standards?

The best way to surface discrepancies between implemented code and testing standards is a post-execution review. It generates structured reports categorizing issues as ERRORS, WARNINGS, and INFO to guide remediations before shipping.

Can I use cross-layer analysis and visual-testing options for multi-phase project reviews?

Yes, you can use cross-layer and visual-testing options for multi-phase project reviews. When configured, these options validate features, tests, and architecture conformance across different layers of the implementation.

Do I need to run code execution before validating plan compliance and artifact quality?

Yes, you need to run code execution before validating plan compliance. The implementation review is applied after code execution across multi-phase projects to assess plan compliance, pattern adherence, and artifact quality.

Why does generated code deviate from the project plan and how do I report it?

Generated code deviates from the project plan due to implementation gaps or pattern mismatches. You can report it by running a post-execution review that outputs structured findings with severities and a final verdict for traceability.