Skill: Consolidate inline report-formatting instructions into shared/reporting.md
Description: .github/workflows/shared/reporting.md already exists as an inline skill for report formatting (h3-only headers, <details> wrapping, run-ID link format), and is imported by 93 workflows. However, at least 42 additional workflows contain their own inline paraphrase of the same guidance ("Use h3 headers... wrap long sections in <details><summary>...") instead of importing the shared skill, creating drift risk (several slightly different wordings/thresholds like >5 items vs >10 items were found) and duplication.
Current usage
- Workflows with inline (non-imported) report-formatting text include:
daily-observability-report.md, daily-byok-ollama-test.md, daily-safe-output-optimizer.md, daily-team-evolution-insights.md, step-name-alignment.md, draft-pr-cleanup.md, daily-agent-of-the-day-blog-writer.md, copilot-pr-prompt-analysis.md, objective-impact-report.md, daily-token-consumption-report.md, terminal-stylist.md, daily-reliability-review.md, api-consumption-report.md, detection-analysis-report.md, delight.md, spec-librarian.md, daily-compiler-quality.md, metrics-collector.md, chaos-pr-bundle-fuzzer.md, daily-performance-summary.md, ai-moderator.md, bot-detection.md, issue-monster.md, typist.md, daily-security-red-team.md, notion-issue-summary.md, copilot-session-insights.md, ci-doctor.md, agentic-token-optimizer.md, stale-pr-cleanup.md, daily-cli-tools-tester.md, daily-regulatory.md, daily-credit-limit-test.md, daily-max-ai-credits-test.md, daily-secrets-analysis.md, daily-fact.md, daily-safe-outputs-conformance.md, daily-model-resolution.md, and others (42 total identified).
- Existing shared component:
shared/reporting.md (already used by 93 workflows) — this recommendation is about migrating the remaining duplicated inline copies, not creating a new file.
Proposed shared component
Reuse existing shared/reporting.md; no new file needed. Optionally add a short migration note in shared/reporting.md's header comment pointing new-workflow authors to prefer the import over inlining the guidance.
Estimated impact
- 42 workflows affected
- ~5-15 lines saved per workflow => 250-500+ lines saved, and eliminates wording drift (e.g., inconsistent
>5 vs >10 item thresholds for collapsing sections)
- Maintenance benefit: report-formatting rules become single-sourced; future changes (e.g., new run-ID link format) apply everywhere via one edit instead of 130+
Migration plan
- Confirm each of the 42 workflows' inline text is semantically equivalent to
shared/reporting.md (spot-check a sample of ~8-10 for meaningful deltas before bulk migration).
- For each workflow, replace the inline paragraph with
imports: [shared/reporting.md] (merging into existing imports: list if present) and remove the duplicated prose from the prompt body.
- Run
make recompile and spot-diff .lock.yml outputs to confirm no unintended prompt content loss.
- Batch the 42 workflows into a few PRs (e.g., 10-15 at a time) to keep diffs reviewable.
Example usage
imports:
- shared/reporting.md
Priority: Medium (42 workflows, low-medium complexity — requires per-file review to confirm text is truly equivalent before removing, since wording varies slightly).
Generated by 🔍 Workflow Skill Extractor · auto · 60.3 AIC · ⌖ 3.43 AIC · ⊞ 7K · ◷
Skill: Consolidate inline report-formatting instructions into shared/reporting.md
Description:
.github/workflows/shared/reporting.mdalready exists as an inline skill for report formatting (h3-only headers,<details>wrapping, run-ID link format), and is imported by 93 workflows. However, at least 42 additional workflows contain their own inline paraphrase of the same guidance ("Use h3 headers... wrap long sections in<details><summary>...") instead of importing the shared skill, creating drift risk (several slightly different wordings/thresholds like>5 itemsvs>10 itemswere found) and duplication.Current usage
daily-observability-report.md,daily-byok-ollama-test.md,daily-safe-output-optimizer.md,daily-team-evolution-insights.md,step-name-alignment.md,draft-pr-cleanup.md,daily-agent-of-the-day-blog-writer.md,copilot-pr-prompt-analysis.md,objective-impact-report.md,daily-token-consumption-report.md,terminal-stylist.md,daily-reliability-review.md,api-consumption-report.md,detection-analysis-report.md,delight.md,spec-librarian.md,daily-compiler-quality.md,metrics-collector.md,chaos-pr-bundle-fuzzer.md,daily-performance-summary.md,ai-moderator.md,bot-detection.md,issue-monster.md,typist.md,daily-security-red-team.md,notion-issue-summary.md,copilot-session-insights.md,ci-doctor.md,agentic-token-optimizer.md,stale-pr-cleanup.md,daily-cli-tools-tester.md,daily-regulatory.md,daily-credit-limit-test.md,daily-max-ai-credits-test.md,daily-secrets-analysis.md,daily-fact.md,daily-safe-outputs-conformance.md,daily-model-resolution.md, and others (42 total identified).shared/reporting.md(already used by 93 workflows) — this recommendation is about migrating the remaining duplicated inline copies, not creating a new file.Proposed shared component
Reuse existing
shared/reporting.md; no new file needed. Optionally add a short migration note inshared/reporting.md's header comment pointing new-workflow authors to prefer the import over inlining the guidance.Estimated impact
>5vs>10item thresholds for collapsing sections)Migration plan
shared/reporting.md(spot-check a sample of ~8-10 for meaningful deltas before bulk migration).imports: [shared/reporting.md](merging into existingimports:list if present) and remove the duplicated prose from the prompt body.make recompileand spot-diff.lock.ymloutputs to confirm no unintended prompt content loss.Example usage
Priority: Medium (42 workflows, low-medium complexity — requires per-file review to confirm text is truly equivalent before removing, since wording varies slightly).