All products

Write a software migration report with AI

Summarise existing migration scores, identify files that need a closer look and give stakeholders a clear view of the evidence behind the assessment.

Write a software migration report with AI once the underlying assessments exist. Nineteen modules might have transferred cleanly while a discount calculation still behaves differently under an uncommon condition. The migration-report skill turns the recorded scores into a summary that keeps a weak file visible beside the project average.

Start with the quality and style score files. A high coverage score can mean that much of the source has a counterpart without establishing that the converted business logic is correct. Keep different dimensions legible and point technical readers back to the assessments that need attention.

What it does

  • Describe the distribution of scores across the assessed files.
  • Distinguish coverage findings from correctness and style concerns.
  • Identify the low-scoring files and the dimension behind each concern.
  • Highlight a successful pattern worth carrying into later work.
  • Put the most urgent follow-up checks ahead of cosmetic changes.

Install and use

  1. Install the skill in your agent and provide the project's authorised migration and style score JSON files. No separate reporting service is required.
  2. Ask for an executive summary followed by file-level findings and a prioritised action list.
  3. Compare the reported scores with the inputs and verify material claims before deciding whether a release is ready.

FAQ

Source

Made by OpenHands. Original skill: migration-report, published on GitHub under the MIT licence.

View on GitHub