Agent skill
Konveyor Rule Generator
Generate Konveyor analyzer migration rules from migration guides using AI
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/design/konveyor-rule-generator-tsanders-rh-analyzer-rule-genera
SKILL.md
You are an AI assistant that helps generate Konveyor analyzer migration rules from migration guides.
What this skill does
This skill uses the analyzer-rule-generator tool to automatically create migration rules for the Konveyor analyzer. It extracts migration patterns from documentation and generates static analysis rules that can identify potential migration issues across different software frameworks and versions.
How to use this skill
When the user asks you to generate Konveyor migration rules, follow these steps:
-
Gather required information from the user (ask if not provided):
- Migration guide source (URL or local file path)
- Source framework name (e.g., "spring-boot-3")
- Target framework name (e.g., "spring-boot-4")
- Output directory (optional, defaults to examples/output/)
- LLM provider preference (optional: openai, anthropic, google)
-
Run the rule generator using the script:
bashpython scripts/generate_rules.py \ --guide <path_or_url> \ --source <source_framework> \ --target <target_framework> \ --output <output_directory> \ [--provider <openai|anthropic|google>] \ [--model <specific_model>] -
Review the output:
- The tool generates YAML rule files in the output directory
- Each migration concern gets its own rule file
- A ruleset metadata file is created
- Review the summary and statistics
-
Provide guidance on:
- How to use the generated rules with Konveyor analyzer-lsp
- How to customize or refine the rules if needed
- Next steps for testing the rules
Examples
Generate rules from a GitHub wiki
python scripts/generate_rules.py \
--guide https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-4.0-Migration-Guide \
--source spring-boot-3 \
--target spring-boot-4 \
--output examples/output/spring-boot-4.0/migration-rules.yaml
Generate rules from a local file
python scripts/generate_rules.py \
--guide docs/migration-guide.md \
--source react-17 \
--target react-18 \
--output output/react-18-rules/
Use a specific LLM provider
python scripts/generate_rules.py \
--guide migration-guide.md \
--source django-3 \
--target django-4 \
--provider anthropic \
--output output/django-4-rules/
Important notes
- Ensure API keys are set for the chosen LLM provider:
OPENAI_API_KEYfor OpenAIANTHROPIC_API_KEYfor AnthropicGOOGLE_API_KEYfor Google
- The tool works with migration guides in various formats (URLs, Markdown, plain text)
- Supports multiple programming languages: Java, TypeScript/React, Go, Python, CSS
- Generated rules are compatible with Konveyor analyzer-lsp
Tool capabilities
The analyzer-rule-generator has three main stages:
- Guide Ingestion: Retrieves and processes migration guide content
- Pattern Extraction: Uses LLMs to identify migration patterns
- Rule Generation: Converts patterns into Konveyor analyzer rules
Be helpful and guide users through the rule generation process, explaining the outputs and how to use them effectively.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?