migration-report
Generate a comprehensive migration report summarizing quality scores and providing recommendations. Use after scoring a migration project.
What this skill does
Generate a comprehensive migration report that summarizes scores and provides actionable insights. **Prerequisites**: Migration quality scores and style scores must exist (see `migration-score-quality` and `migration-score-style` skills). ## Report Structure ### 1. Executive Summary - Overall migration health (High/Medium/Low confidence) - Key statistics: total files, average scores, score distribution - One-paragraph assessment for stakeholders ### 2. Score Overview #### Coverage Statistics - Average coverage score - Files with coverage < 3 (needs attention) - Files with coverage = 5 (complete) #### Correctness Statistics - Average correctness score - Files with correctness < 3 (needs attention) - Files with correctness = 5 (verified) #### Style Statistics - Average style score per attribute - Common style issues identified ### 3. Risk Assessment Categorize files into: - **Green**: Coverage ≥ 4, Correctness ≥ 4, Style ≥ 4 - **Yellow**: Any score between 3-4 - **Red**: Any score < 3 ### 4. Notable Findings #### Strengths - What was migrated well - Good patterns to replicate #### Weaknesses - Common issues across files - Patterns to avoid ### 5. Recommendations Prioritized action items: 1. **Critical** — Files with scores < 3 2. **Important** — Files with scores 3-4 3. **Nice to have** — Style improvements for green files ### 6. Detailed Scores Include the raw scores for reference (or link to score files). ## Output Format Generate the report as a Markdown file: ```markdown # Migration Quality Report **Generated**: 2024-01-15 **Project**: Customer Management System **Source**: COBOL (45 files) **Target**: Java (62 files) ## Executive Summary Migration is at **MEDIUM confidence** with average coverage of 4.2/5 and correctness of 4.0/5. Three files require immediate attention due to incomplete business logic migration. ## Score Overview ### Coverage - Average: 4.2/5 - Complete (5): 28 files (62%) - Needs attention (<3): 3 files (7%) ... ``` ## Tone and Audience - Write for technical stakeholders (architects, tech leads) - Be specific about issues (cite file names, line numbers if relevant) - Provide actionable recommendations, not vague suggestions - Acknowledge good work, not just problems ## Data Sources Read scores from: - `migration_score.json` — Coverage and correctness scores - `style_score.json` — Style evaluation scores - `migration_mapping.json` — File mapping (for counts) ## Example Recommendations **Good:** > "CALC001.java has coverage 2/5 because batch processing logic in > CALC001.cbl lines 150-200 was not migrated. Implement the > `processBatch()` method to match COBOL paragraph PROCESS-BATCH." **Bad:** > "Some files need more work."
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.