wolfe-arch

Detect architecture decision record violations in code repositories and propose new ADRs.

Updated Jun 15, 2026

Search Tags:#code review #software architecture #repository management #ADR compliance #architecture enforcement

Ready to run

npx skills add https://github.com/jdforsythe/wolfe-pack --skill wolfe-arch

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: wolfe-arch
Source: https://github.com/jdforsythe/wolfe-pack/tree/main/templates/bots/wolfe-arch
Command: npx skills add https://github.com/jdforsythe/wolfe-pack --skill wolfe-arch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the detection and enforcement of architecture decision record (ADR) compliance in code repositories, reducing the risk of violations and ensuring architectural integrity.

Core Features & Use Cases

Automated ADR Compliance: Identifies and flags violations of architectural decisions in the codebase.
Decision Documentation: Documents new architecture decisions and proposes new ADRs when needed.
Use Case: After merging a new feature, this Skill checks the codebase for any violations of established ADRs, such as unauthorized dependencies or service boundaries, and reports them for review.

Quick Start

Invoke the wolfe-arch skill with the specific area to check, e.g., /wolfe-arch backend.

Frequently Asked Questions about wolfe-arch

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

FAQPage Schema

How do I automate architecture decision record compliance checks in my code repository?▼

Automating architecture decision record (ADR) compliance involves scanning your code repository to identify and flag violations of established architectural decisions. This process checks for unauthorized dependencies or boundary breaches and reports them for review.

How does automated ADR enforcement detect architectural violations after a feature merge?▼

Automated ADR enforcement detects violations by running verification commands against repository code and metadata. It identifies unauthorized dependencies or service boundary breaches, flags them as violations, and proposes new ADRs when undocumented architectural decisions are found.

Can I use architecture enforcement tools to document new architectural decisions automatically?▼

Yes, architecture enforcement tools can document new decisions by proposing new ADRs. When the verification process identifies architectural choices that lack formal documentation, it generates proposals to ensure all decisions are recorded and governed.

What is the best way to enforce service boundaries and prevent unauthorized dependencies using ADRs?▼

The best way to enforce service boundaries and prevent unauthorized dependencies is to run automated ADR compliance checks. This identifies code that violates established architectural decisions, ensuring repository integrity and adherence to documented service boundaries.

Do I need repository access and verification commands to enforce ADR compliance?▼

Yes, enforcing ADR compliance requires access to the repository's code and metadata, plus the ability to run verification commands. This access allows the enforcement process to scan for violations and validate architectural decisions effectively.