Architecture Impact

Identify architecture documentation impacts from code changes in HyperFleet component repositories.

5|17|Updated Oct 29, 2025

Search Tags:#architecture #documentation #pr-review #impact-analysis #code-changes #hyperfleet

Ready to run

npx skills add https://github.com/openshift-hyperfleet/hyperfleet-claude-plugins --skill architecture-impact

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Architecture Impact
Source: https://github.com/openshift-hyperfleet/hyperfleet-claude-plugins/tree/main/hyperfleet-devtools/skills/architecture-impact
Command: npx skills add https://github.com/openshift-hyperfleet/hyperfleet-claude-plugins --skill architecture-impact

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git.

What problem does it solve?

Analyzes architecture-impact caused by code changes in HyperFleet component repositories and determines whether architecture documentation in the architecture repository needs to be updated.

Core Features & Use Cases

Directory-based analysis across HyperFleet components (hyperfleet-api, hyperfleet-sentinel, hyperfleet-adapter, hyperfleet-broker).
Supports analysis of uncommitted changes, git ranges, and last N commits with a single comprehensive pass.
Caches and updates the architecture repository locally to ensure up-to-date context for impact decisions.
Generates a structured report detailing affected documents and recommended updates.

Quick Start

Provide a git range or last N commits to start the analysis, e.g., --range main..HEAD or --last 5.

Frequently Asked Questions about Architecture Impact

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

FAQPage Schema

How do I analyze the architecture impact of code changes in my repository?▼

To analyze architecture impact, you can assess uncommitted changes, specify a git range, or analyze the last N commits. This process identifies code modifications and determines whether architecture documentation requires corresponding updates.

What is architecture impact analysis and when do I need it?▼

Architecture impact analysis identifies whether code changes in component repositories affect existing architecture documentation. You need this process when updating code to ensure your architecture repository stays synchronized with structural modifications.

How do I check if code changes require documentation updates?▼

You can check documentation update requirements by running a directory-based analysis across component repositories. The tool generates a structured report detailing affected documents and recommended updates based on your code changes.

Do I need git to perform an architecture impact assessment?▼

Yes, git is a required dependency for architecture impact assessment. The tool uses git to process uncommitted changes, specified commit ranges, or the last N commits to evaluate documentation impacts.

What is the best way to review uncommitted changes for architecture impacts?▼

The best way to review uncommitted changes is using a comprehensive directory-based analysis across component repositories. This approach evaluates the changes in a single pass and produces a structured impact report.

Can I use architecture impact analysis for specific git commit ranges?▼

Yes, you can use architecture impact analysis for specific git commit ranges by providing parameters like --range main..HEAD. The tool evaluates the specified commits and identifies affected architecture documents.