lina-review

Enforce specification compliance for code and OpenSpec changes in LinaPro projects.

147|28|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/linaproai/linapro --skill lina-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lina-review
Source: https://github.com/linaproai/linapro/tree/main/.agents/skills/lina-review
Command: npx skills add https://github.com/linaproai/linapro --skill lina-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

LinaPro projects often face spec drift and non-compliant code being merged or archived, leading to technical debt and inconsistent system behavior. This skill eliminates that risk by enforcing strict specification compliance checks for all code and OpenSpec changes at critical workflow stages.

Core Features & Use Cases

  • Automated Workflow Integration: Triggers automatically after /opsx:apply task completion, lina-feedback fix completion, and pre-/opsx:archive to catch issues early.
  • Rule-Driven Compliance Checks: Uses AGENTS.md and .agents/rules/*.md as the sole source of truth for project specs, covering backend Go, frontend, testing, i18n, data permissions, and more.
  • Structured Audit Reports: Generates clear reports with severity levels (blocking/warning), validation evidence, and actionable fix recommendations.
  • Use Case: When a developer finishes a backend feature via /opsx:apply, this skill reviews all changed Go files, API contracts, and related tests against the project's backend-go.md and api-contract.md rules to block non-compliant code before the next task starts.

Quick Start

Use the lina-review skill to audit all code changes from your current /opsx:apply task against the project's specification rules.

Frequently Asked Questions about lina-review

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

FAQPage Schema
How do I check code compliance against project specifications before merging?

Code compliance is checked by validating changes against domain-specific rules defined in AGENTS.md and .agents/rules/*.md files, generating structured audit reports with severity classifications and fix recommendations.

How does spec compliance review work in GoFrame backend development?

Spec compliance review for GoFrame backend development validates changed Go files, API contracts, and tests against backend-go.md and api-contract.md rules to block non-compliant code before task completion.

Can I automate code review for OpenSpec changes before archiving?

Code review for OpenSpec changes can be automated by triggering compliance checks pre-/opsx:archive, after /opsx:apply task completion, and after lina-feedback fix completion to catch issues early.

What specification domains does the LinaPro code audit cover?

The LinaPro code audit covers backend Go, frontend, testing, i18n, data permissions, and other specification domains defined within the project's rule files.

Do I need AGENTS.md rule files to perform a spec compliance audit?

AGENTS.md and .agents/rules/*.md files are required as the sole source of truth to perform spec compliance audits, providing the domain-specific validation rules for backend, frontend, and testing checks.

Why does my code review report show blocking severity levels?

Code review reports show blocking severity levels when changed code violates critical specification rules defined in the project's rule files, requiring actionable fixes before proceeding.