skills.rest
stolostron
stolostronOFFICIAL
Explore all skills by this author →
WebsiteGitHub

acm-qe-code-analyzer

Analyze GitHub PR diffs for ACM repositories to identify code changes and testing scenarios.

3|4|Updated Jul 25, 2025
Search Tags:#code review#GitHub#PR analysis#ACM#PR diff
One-click install
npx skills add https://github.com/stolostron/acm-ai-qe --skill acm-qe-code-analyzer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: acm-qe-code-analyzer
Source: https://github.com/stolostron/acm-ai-qe/tree/main/.claude/skills/acm-qe-code-analyzer
Command: npx skills add https://github.com/stolostron/acm-ai-qe --skill acm-qe-code-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, acm-source, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill simplifies understanding of code changes in ACM-related GitHub repositories, focusing on identifying what has changed and what needs to be tested without running the full JIRA-to-Polarion test case generator pipeline.

Core Features & Use Cases

  • PR Diff Analysis: Analyze changes in code, UI, components, and more from GitHub PR diffs.
  • Default Repos: Defaults to stolostron/console and kubevirt-ui/kubevirt-plugin when no specific repo is specified.
  • Use Case: Quickly determine what has changed in a PR for stolostron/console or kubevirt-ui/kubevirt-plugin, and identify potential testing scenarios.

Quick Start

Use the acm-qe-code-analyzer skill to analyze PR #1234 and understand what changed: analyze PR #1234.

Frequently Asked Questions about acm-qe-code-analyzer

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

FAQPage Schema
How do I analyze a GitHub PR diff to identify code and UI changes?▼

To analyze a GitHub PR diff, you can process the pull request changes to identify code modifications, UI updates, and potential testing scenarios. This Skill parses PR diffs for ACM-related repositories to pinpoint exactly what changed.

What is the best way to review PR changes in stolostron/console without running the full test generator?▼

The best way to review PR changes without running the full JIRA-to-Polarion test case generator is to analyze the GitHub PR diff directly. This approach quickly isolates component modifications and identifies necessary testing scenarios.

Do I need the gh CLI to analyze pull requests for ACM repositories?▼

Yes, you need the gh CLI installed and access to the acm-source MCP for source verification. These dependencies are required to fetch GitHub PR diffs and accurately analyze the ACM-related code changes.

Can I analyze pull requests for repositories other than kubevirt-ui/kubevirt-plugin?▼

Yes, you can analyze pull requests for other ACM-related repositories by specifying the target repository. If no specific repository is provided, the analysis defaults to stolostron/console and kubevirt-ui/kubevirt-plugin.

Related Skills

Explore More Software Engineering Skills→
stolostronstolostron
3

acm-data-enricher

Enrich ACM test failure data with AI analysis and git history.

Official
Advanced
stolostronstolostron
3

generate-test-case

Generate Polarion-ready test cases from JIRA tickets via a 6-phase pipeline.

Official
Advanced
stolostronstolostron
3

batch

Generate test cases for multiple JIRA tickets and summarize results.

Official
Advanced
lee-tolee-to
56

aif-review

Inspect git diffs and PR metadata to identify code defects and quality issues.

Community
Advanced