(check)
| 67 | } |
| 68 | |
| 69 | function deriveCheckWhy(check) { |
| 70 | if (check.why) { |
| 71 | return check.why; |
| 72 | } |
| 73 | |
| 74 | if (check.category === "manifest") { |
| 75 | return "Manifest issues reduce trust because Codex may not discover or represent the plugin correctly."; |
| 76 | } |
| 77 | |
| 78 | if (check.category === "skill-structure") { |
| 79 | return "Skill structure issues reduce trigger quality and make the skill harder to trust or maintain."; |
| 80 | } |
| 81 | |
| 82 | if (check.category === "budget") { |
| 83 | return "Budget pressure matters because always-loaded or frequently-loaded text can make the workflow feel expensive fast."; |
| 84 | } |
| 85 | |
| 86 | if (check.category === "measurement") { |
| 87 | return "Weak measurement means you are still steering with estimates instead of evidence."; |
| 88 | } |
| 89 | |
| 90 | if (check.category === "best-practice") { |
| 91 | return "Best-practice gaps usually do not break the workflow immediately, but they make the skill harder to understand and improve."; |
| 92 | } |
| 93 | |
| 94 | if (check.category === "complexity") { |
| 95 | return "Complexity findings matter because they increase review cost and make generated or helper code harder to change safely."; |
| 96 | } |
| 97 | |
| 98 | if (check.category === "readability") { |
| 99 | return "Readability issues slow engineers down during review, debugging, and follow-up edits."; |
| 100 | } |
| 101 | |
| 102 | if (check.category === "code-quality") { |
| 103 | return "Code-quality findings matter because helper scripts and supporting code are part of the user experience too."; |
| 104 | } |
| 105 | |
| 106 | return "This finding affects confidence, clarity, or trust in the overall workflow."; |
| 107 | } |
| 108 | |
| 109 | function buildDeductions(checks) { |
| 110 | return checks |
no outgoing calls
no test coverage detected