Final Report.prompt
--- name: final-report description: "Generate the final translation report with per-file and repo-level confidence scores, test coverage, and security findings." argument-hint: "Provide the translation session ID for the final report" model: Claude Sonnet 4.6 (copilot) agent: translation-conductor tools: [search, read, changes] --- # Final Translation Report ## Context All translation phases are complete. Compile the final report for the translated repository. ## Source - **Source Repo:** ${input:source_repo} - **Source Language:** ${input:source_language} - **Target Language:** ${input:target_language} ## Instructions Compile the final report covering all sections below. Use data from `artifacts/plans/translation/manifest.json`, validation results, and security findings. ## Report Sections ### 1. Executive Summary - Total files translated, total LOC - Overall repo confidence score - Total tests written, pass rate - Security findings summary - Time/effort metrics ### 2. Per-File Confidence Matrix | Source File | Target File | LOC | Confidence | Status | Notes | |-------------|-------------|-----|------------|--------|-------| | ... | ... | ... | 0.XX | ✅/âš ï¸/⌠| ... | ### 3. Validation Summary - Layer-by-layer aggregate scores - Files requiring manual review - Known behavioral differences ### 4. Test Coverage Report - Unit tests: count, pass rate, coverage % - Integration tests: count, pass rate - Functional tests: count, pass rate - Untested areas and recommendations ### 5. Security Review Summary - STRIDE threat model findings - Dependency vulnerability scan results - Compliance checkpoint results - Remediation actions taken ### 6. Translation Decisions Log - Major architectural decisions - Framework/library choices with rationale - Patterns that were redesigned (not 1:1 translated) - Areas where source language features had no direct equivalent ### 7. Recommendations - Files recommended for manual review - Performance optimization opportunities - Suggested improvements over source codebase - Follow-up tasks and technical debt items ### 8. Repo Confidence Score Weighted average: Σ(LOC × Score) / Σ(LOC) Display with breakdown by confidence band: - High (≥0.9): X files (Y% of LOC) - Medium (0.7–0.89): X files (Y% of LOC) - Low (0.5–0.69): X files (Y% of LOC) - Critical (<0.5): X files (Y% of LOC) ## Output Format A single Markdown report (`artifacts/plans/translation/final-report.md`) containing all 8 sections above with tables, confidence scores, and actionable recommendations.
fill the variables
This prompt has 3 variables. Pro fills them into a ready-to-paste prompt for you — no manual find-and-replace.
{input:source_repo}{input:source_language}{input:target_language}
Unlock with Pro →when to use it
Community prompt sourced from the open-source GitHub repo kennedym-ds/copilot_orchestrator (MIT). A "Final Report.prompt" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
productivitycommunitydeveloper
source
kennedym-ds/copilot_orchestrator · MIT
more in Productivity
Productivity✓ tested
Summarize a doc into decisions & actions
chief of staff who extracts what to DO, not just what was said
Productivity✓ tested
Draft a reply to a hard email
calm, direct communicator who de-escalates without caving
Productivity✓ tested
Turn a brain-dump into a weekly plan
planning coach who protects your focus, not just your calendar