Workflow Skill Extractor — Shared Component Opportunities Report

[github-actions[bot]]

Summary

Analyzed 205 workflow files across .github/workflows/ to identify reusable shared component opportunities. The repository already has a healthy shared component ecosystem (shared/ directory with 50+ components), with reporting.md (50 imports), observability-otlp.md (22), github-guard-policy.md (19), and jqschema.md (18) being the most popular.

Three high-impact gaps were identified and filed as issues.

---

Methodology

1. Loaded /tmp/gh-aw/agent/workflow-index.json (205 workflows)
2. Counted import frequencies across all workflows to identify existing component adoption
3. Identified clusters of similar workflows NOT sharing components despite similar patterns
4. Validated candidates by reading actual frontmatter to confirm duplication
5. Checked existing shared/ for any overlapping components to avoid duplicates

---

Top 3 Recommendations

🔴 HIGH — #29292: shared/daily-issue-base.md

Pattern: Scheduled workflows that detect code quality issues and create GitHub issues (not discussions).
Duplication: tracker-id + skip-if-match + activation-app + reporting + create-issue safe-outputs
Affected workflows (confirmed): architecture-guardian, breaking-change-checker, daily-file-diet, daily-testify-uber-super-expert, refactoring-cadence, spec-librarian
Impact: ~12 workflows, ~15 lines/workflow, analogue to existing daily-audit-base.md

---

🔴 HIGH — #29294: shared/daily-pr-base.md

Pattern: Daily automated code improvement workflows that create pull requests.
Duplication: skip-if-match (PR check) + activation-app + create-pull-request safe-outputs + reporting
Affected workflows (confirmed): code-simplifier, dead-code-remover, code-scanning-fixer, slide-deck-maintainer, ubuntu-image-analyzer, unbloat-docs, daily-rendering-scripts-verifier
Impact: ~15 workflows, ~12–18 lines/workflow

---

🟡 MEDIUM — #29295: shared/pr-review-base.md

Pattern: Slash-command or PR-triggered code review workflows.
Duplication: github-guard-policy + pr-code-review-config + cli-proxy tools + create-pull-request-review-comment
Affected workflows: grumpy-reviewer, pr-nitpick-reviewer, security-review, refiner, pr-triage-agent, org-health-report
Impact: ~6 workflows, ~10–15 lines/workflow, consistency across all review bots

---

Coverage Map

Shared Component	Imports	Already Exists
shared/reporting.md	50	✅
shared/daily-audit-base.md	53	✅
shared/observability-otlp.md	22	✅
shared/github-guard-policy.md	19	✅
shared/jqschema.md	18	✅
shared/activation-app.md	11	✅
shared/daily-issue-base.md	0 (needed)	❌ New
shared/daily-pr-base.md	0 (needed)	❌ New
shared/pr-review-base.md	0 (needed)	❌ New

---

Notes

• The daily-audit-base.md pattern (53 users) is mature and serves discussion-based daily workflows well; the gaps are specifically in the issue-output and PR-output daily workflow categories
• cache-memory is used by 65+ workflows but configurations vary too widely for a single shared bundle; the existing simple cache-memory: true default already works
• No duplicate recommendations were raised — all 3 proposals fill genuine gaps in shared/

References: §25163549011

Generated by Workflow Skill Extractor · ● 4.3M · ◷

• expires on May 7, 2026, 11:56 AM UTC

[github-actions[bot]]

This discussion has been marked as outdated by Workflow Skill Extractor.

A newer discussion is available at Discussion #30754.