Architecture Impact
Architecture Impact Analyzer
This skill analyzes code changes in HyperFleet component repositories and determines whether architecture documentation in the openshift-hyperfleet/architecture repository needs to be updated.
When to Use This Skill
This skill activates automatically when users:
- Ask "analyze architecture impact"
- Ask "check if docs need update"
- Ask "should I update architecture docs?"
- Request analysis of documentation impact from code changes
- Want to know if their PR requires architecture documentation updates
Prerequisites
Zero setup required!
More from openshift-hyperfleet/hyperfleet-claude-plugins
jira story point estimator
Estimates story points for JIRA tickets by analyzing complexity, scope, and comparing to historical team data. Activates when users ask to estimate, point, or size a ticket, or ask "how many points should this be?
15jira ticket creator
Creates well-structured JIRA tickets in the HYPERFLEET project with required fields including What/Why/Acceptance Criteria, story points, and activity type. Activates when users ask to create a ticket, story, task, or epic.
13jira-story-pointer
Estimates story points for JIRA tickets by analyzing complexity, scope, and comparing to historical team data. Activates when users ask to estimate, point, or size a ticket, or ask "how many points should this be?
2review-pr
Review a PR with JIRA validation, architecture checks, impact analysis, and interactive recommendations
1hyperfleet architecture
Answers questions about HyperFleet architecture, design patterns, versioning strategies, cluster lifecycle, event-driven architecture, adapter framework, and git workflow by fetching docs from the openshift-hyperfleet/architecture GitHub repository.
1jira ticket triage
Validates JIRA tickets have required fields and quality standards for sprint planning.
1