pr-architecture-review

Identify architecture contract violations in Ansible Jane project PRs.

1|Updated Apr 2, 2026

Search Tags:#documentation #code-quality #android #kotlin #architecture-review #pr-review #contract-checks

Ready to run

npx skills add https://github.com/leogallego/ansible-jane --skill pr-architecture-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-architecture-review
Source: https://github.com/leogallego/ansible-jane/tree/main/skills/pr-architecture-review
Command: npx skills add https://github.com/leogallego/ansible-jane --skill pr-architecture-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PRs often drift from documented architecture contracts; this skill provides automated checks to enforce compliance during code reviews.

Core Features & Use Cases

Review PRs against the architecture service contracts defined in docs/architecture/service-contracts.md.
Auto-loads relevant Kotlin/Android skills based on the files touched in the PR.
Guides reviewers through contract checks and highlights violations to maintain architectural integrity.
Use Case: When a PR changes module boundaries or layer interfaces, run this skill to surface contract violations before merge.

Quick Start

Run the PR architecture-review process on your branch to identify and log any violations.

Frequently Asked Questions about pr-architecture-review

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

FAQPage Schema

How do I automate architecture contract checks in pull requests?▼

Architecture contract checks in pull requests are automated by verifying code changes against documented layer discipline, interface contracts, module boundaries, and naming conventions. The skill surfaces contract violations before merge to maintain architectural integrity.

What is a PR architecture review and how does it work?▼

PR architecture review is the process of validating pull request changes against architecture service contracts defined in documentation. It auto-loads relevant Kotlin and Android skills based on changed files to check layer discipline, interface contracts, and module boundaries.

How do I enforce module boundaries and layer discipline in Kotlin Android projects?▼

Module boundaries and layer discipline in Kotlin Android projects are enforced by running automated PR reviews against architecture service contracts. The process identifies violations in interface contracts and naming conventions before code merge.

Does this PR review process work with existing architecture documentation?▼

Yes, the PR review process works with existing architecture documentation by checking code changes against the service contracts defined in docs/architecture/service-contracts.md. It directly references documented layer discipline and interface boundaries.

Can I automatically verify interface contracts and naming conventions in code reviews?▼

Interface contracts and naming conventions are automatically verified during code reviews by applying architecture contract checks to the changed files. The skill highlights any violations found in the pull request before merge.

What's the best way to prevent architecture drift before merging code changes?▼

Preventing architecture drift before merging code changes is best achieved by running automated architecture contract reviews on your branch. This surfaces contract violations in module boundaries and layer interfaces early in the review cycle.