archyl-review

Analyze code changes against Archyl's C4 model and conformance rules.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architectural review for PR changes, surfacing violations, boundary issues, and stale contracts before code is merged.

Core Features & Use Cases

  • Analyze code changes against Archyl's C4 model, conformance rules, and API contracts to surface architectural issues before merge.
  • Provide structured PR feedback highlighting violations, boundary crossings, and recommended ADRs.
  • Support architecture-aware code reviews during PRs across services.

Quick Start

Invoke the archyl-review skill during PR reviews to receive architecture-focused feedback on the changes.

Frequently Asked Questions about archyl-review

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

FAQPage Schema
How do I automate architecture review for pull requests?

To automate architecture review for pull requests, analyze code changes against C4 model boundaries and conformance rules to surface architectural violations before merging.

What are API conformance checks in PR reviews?

API conformance checks in PR reviews detect stale contracts and boundary crossings by evaluating code changes against existing API contracts and architecture rules.

How do I detect architectural violations before merging code?

Detect architectural violations before merging by applying review feedback that catches unauthorized tech usage, boundary crossings, and stale API contracts during the PR process.

How does C4 model integration work for code review feedback?

C4 model integration for code review feedback evaluates PR changes against defined container and component boundaries, identifying boundary crossings and recommending ADRs for structural issues.

Can I catch unauthorized technology usage during pull request reviews?

You can catch unauthorized technology usage during pull request reviews by evaluating code changes against a technology radar, flagging unauthorized tech before code is merged.

What is the best way to structure architecture feedback for pull requests?

The best way to structure architecture feedback for pull requests is to provide actionable feedback highlighting violations, boundary crossings, and recommended ADRs based on conformance rules.